Lector de Feeds

Publication date: 05 Aug 2026
Type: bugfix
Affected Mageia releases : 10 , 9
Description netprofile sent messages to com.mandriva.user instead of org.mageia.user. This update fixes the issue. References

• https://bugs.mageia.org/show_bug.cgi?id=36033

SRPMS 10/core

• netprofile-0.29.1-1.mga10

9/core

• netprofile-0.29.1-1.mga9

We started a series of blog posts. Ideas, applications, processes, customizations, contributions about our distribution that are relevant to our users, bringing the use of Mageia closer to everyone. We certainly hope that these new publications are of interest to you, you can share them on social networks, your personal blog, website, news sites or any other place that serves to show the qualities of Mageia!

Prologue

Today we’re going to talk about this application which, although somewhat forgotten by many, is a great low-resource alternative for managing multiple messaging protocols simultaneously. In Mageia, it’s very well packaged with many plugins that you won’t find in other distributions and that complement Pidgin very well, allowing you to use it like modern messaging apps.

Pidgin is cross-platform and multi-protocol, which means that if you add what you need, you’ll have a multitude of messaging applications in one.

On the other hand, resource optimization is such that the impact on the system is truly minimal. Just look at some data from two of the most requested applications by the average user: WhatsApp and Telegram, for example.

• • Opening Telegram will consume 300 to 400MB of your computer’s RAM.

• • Opening WhatsApp will consume 700 to 900MB of your computer’s RAM—a truly outrageous amount for a messaging app… Of course, most of these versions are built on Electron, and their optimization is about as good as Mageia is for Windows…

Opening Pidgin with both accounts configured consumes 90 to 150 MB of your computer’s RAM, at most, so as you can see, in terms of performance and resource optimization, it’s highly recommended…

After this, Pidgin has its plugins. It’s highly recommended to leave the “History” plugin activated, which allows you to save conversations in the log. Note that it’s advisable not to delete conversations from the conversation window, which you can find in the “View History” option in each conversation’s menu.

Installation

Installation in Mageia is very simple, although some accounts may require the installation of a few extra packages. There are two ways to do it: through the software manager or via the terminal. Let’s get started:

• • Terminal: It is recommended to have the Blogdrake community repositories enabled for some packages. Enter the terminal as root and write: “urpmi pidgin pidgin-telegram-tdlib purple-gowhatsapp purple-telegram-tdlib pidgin-libnotify pidgin-indicator pidgin-window_merge pidgin-wemoji-theme”. With this command, pidgin and plugins for telegram, whatsapp and a complete emoji theme will be installed.

• • Software Manager: Go to the Start menu and search for “Install or Remove Apps.” Once there, make sure both search filters are set to “All.” Next, we install the following packages: “pidgin pidgin-telegram-tdlib” “pidgin-wemoji-theme” “purple-gowhatsapp” “purple-telegram-tdlib” “pidgin-libnotify” “pidgin-indicator” “pidgin-window_merge”. As before, this will install plugins and the emoji theme.

Configure Pidgin to manage these two messages It’s relatively simple. As soon as you launch the application, a greeting and a window to start configuring the accounts will appear. Note that Pidgin supports many other communication protocols, such as Gadu-Gadu, Google Talk, IRC, XMPP, etc. For more information about them and how to install them, you can visit the “official Pidgin website. Let’s get started:

Telegram

In the accounts section, tap “Add.” In the next window, choose the “Telegram (tdlib)” protocol. Then, in the “Username” field, enter your phone number with the international code. For example, in my case, from Spain, it would be 34669543111, and tap “Accept” or “Add.” After this, a pop-up window will appear to add the code that Telegram sends to the mobile application. The Telegram account is now set up.

Whatsapp

In the accounts section, tap “Add”, and in the next window choose the “Whatsapp” protocol. Next, in the “Username” field, enter your phone number in international code, and now comes the important part followed by “@s.whatsapp.net”, for example, 34669543111@s.whatsapp.net. After this, a window will appear with a QR code to add the session from the mobile app.

Extra configuration for GTK themes, dark mode in Pidgin

For desktop environments other than Plasma, if Pidgin doesn’t pick up the default dark theme from the desktop environment preferences, you can try closing Pidgin after configuring the accounts and installing the packages:

• • “gtk-chtheme”. This is an application that will allow you to change the themes of GTK applications.

• • “gtk2-theme-engines”. Installs various GTK themes for GTK applications.

• • Open the GTK themes application and select the “Nodoka-Midnight” theme.

This seems to be the theme that best integrates dark mode into Pidgin.

• • Go to your home folder and find the file “.gtkrc-2.0” (you will need to show hidden files to find it). Remember to remove the period from the name once copied so that the theme applies correctly to Pidgin, leaving the name as “gtkrc-2.0”.

• • Copy that file to the “.purple” folder, which is where everything related to Pidgin is located.

• • Restart, and then open Pidgin normally. It should now display the dark theme.

• • Some screenshots:

We previously installed an expanded emoji theme. To activate it, go to Preferences, then to “Themes > Emoji Theme,” and select the theme. It will appear as WhatsApp/iOS Emojis.

Extra access, shortcuts, and other features.

• • From the main window, you can search for a chat using “Ctrl+f”. If, for example, we have the same name on two different accounts (WhatsApp and Telegram), Pidgin will tell us which account we want the chat from.

    From a chat window, use “Ctrl+F” to search within the current chat.

    From the chats window, use “Ctrl+M” to open a new chat or search for one to open a conversation.

    From the “Conversation > View History” menu, you can view the history of the current chat (remember to enable the “History” plugin in the plugins section first). –>

  • From the main “Friends List” window, press “Ctrl-p” to open preferences.

Add-ons

• • History: Shows previous chat conversations. Enter the last conversation before starting the new one.

• • Libnotify Popus (not to be confused with Libnotify+): Displays notifications using libnotify

• • Message notification: Allows notification of unread messages.

• • New line: Adds a horizontal line to separate old and new conversations.

• • Window-merge: This plugin allows you to merge the “friends” and “chats” windows.

You can configure these plugins from the “Configure Plugin” option just below the window.

We hope you found this tutorial interesting. It shows you how to configure and use an application that, while not very well-known, is a gem for managing messaging from your PC with minimal resources. Best of all, it’s available from the Mageia and BlogDrake!!!.

repositories.

Empezamos una serie de entradas en el blog. Ideas, aplicaciones, procesos, personalizaciones, aportes sobre nuestra distribución que son relevantes para nuestros usuarios, acercando el uso de Mageia para todos. Esperamos sin duda que estas nuevas publicaciones sean de tu interés, puedes compartirlas en redes sociales, tu blog personal, web, sitios de noticias o cualquier otro lugar que sirva para mostrar las cualidades de Mageia!

Prólogo

Hoy vamos a hablar de esta aplicación que aunque está un poco olvidada por muchos, es una gran alternativa de muy bajos recursos para gestionar varios protocolos de mensajería al mismo tiempo. En Mageia está muy bien empaquetada con muchos plugins que no encontrarás en otras distros y que complementan muy bien a Pidgin para poder usarlo como las apps de mensajería modernas.

Pidgin es multiplataforma y multiprotocolo, lo que significa, que si añades lo que te hace falta, tendrás un montón de aplicaciones de mensajería en una sola. Por otro lado, la optimización de recursos, es tal, que el impacto en el sistema es realmente ínfimo, basta con ver algunos datos de dos de las aplicaciones más requeridas por un usuario medio, Whatsapp y Telegram por ejemplo.

• Abrir Telegram, consumirá de 300 a 400mb de Ram de tu equipo.
• Abrir Whatsapp, consumirá de 700 a 900mb de Ram de tu equipo,una auténtica burrada para una app de mensajería…Claro, que la mayoría de estas versiones están construidas en Electron, y de optimización tienen… lo que Mageia de Windows…

Abrir Pidgin con las dos cuentas configuradas consume de 90 a 150 mb de Ram de tu equipo, tirando por lo alto, así que por lo que ves, en rendimiento y optimización de recursos es más que recomendable…

Después de esto, en Pidgin tenemos sus plugins. Es muy recomendable dejar activado el plugin “Histórico”, que permite guardar las conversaciones en el registro, ojo, lo que si se aconseja es no borrar las conversaciones de la ventana de las mismas, que podrás encontrar en la opción “Ver historial” en el menú de cada conversación.

Instalación

En Mageia la instalación es muy sencilla, aunque ante el posible requerimiento de algunas cuentas habrá que instalar algunas paquetes extras. Hay dos formas de realizarla, por medio del gestor de software o por terminal, manos a la obra:

• Terminal: Recomendable tener activados los repositorios comunitarios de blogdrake para algunos paquetes. Entrar como root a la terminal y escribir: “urpmi pidgin pidgin-telegram-tdlib purple-gowhatsapp purple-telegram-tdlib pidgin-libnotify pidgin-indicator pidgin-window_merge pidgin-wemoji-theme”..Con este comando, se instalarán pidgin y plugins para telegram, whatsapp y un tema completo de emojis.

• Gestor de software: Ir a menú de inicio y buscar “Instalar y quitar aplicaciones”. Una vez dentro, comprobar que tenemos los dos filtros de búsqueda en “Todos”. Después instalamos los siguientes paquetes: “pidgin pidgin-telegram-tdlib” “pidgin-wemoji-theme” “purple-gowhatsapp” “purple-telegram-tdlib” «pidgin-libnotify» «pidgin-indicator» «pidgin-window_merge». Como antes con esto instalaremos plugins y tema de emojis.

Configurar Pidgin para gestionar estas dos mensajerías es relativamente sencillo, ya desde que iniciemos la aplicación, aparecerá un saludo y una ventana para empezar a configurar las cuentas. Indicar, que Pidgin sirve para otros muchos protocolos de comunicación, como Gadu-Gadu, Google Talk, IRC, Xmpp, etc, para más información sobre ellos y como instalarlos puedes visitar el «sitio oficial de Pidgin. Vamos allá:

Telegram

En el apartado de cuentas pulsar “Añadir”, en la ventana siguiente elegir el protocolo “Telegram (tdlib)”. Después en la opción “Nombre de usuario” introducir el número de teléfono en clave internacional, por ejemplo, en mi caso de España sería 34669543111 y aceptar o añadir. Después de esto aparecerá una ventana emergente para añadir el código que envía telegram en la aplicación móvil. La cuenta de Telegram ya está configurada.

Whatsapp

En el apartado de cuentas, pulsar “Añadir”, en la ventana siguiente elegir el protocolo “Whatsapp”. Después en la opción “Nombre de ususario”, introducir el número de teléfono en clave internacional, y ahora viene lo importante seguido de “@s.whasapp.net, por ejemplo 34669543111@s.whatsapp.net. Después de esto aparecerá una ventana con un código Qr para añadir la sesión desde la aplicación móvil.

Extra de configuración, para temas Gtk, modo oscuro en Pidgin

Para entornos de escritorio distintos a Plasma, si Pidgin no coge el tema oscuro por defecto de las preferencias del entorno de escritorio, puedes probar a cerrar Pidgin después de configurar las cuentas e instalar los paquetes:

• «gtk-chtheme». Es una aplicación que te permitirá cambiar los temas de las aplicaciones Gtk.
• «gtk2-theme-engines». Instala varios temas gtk para aplicaciones Gtk.
• Entrar en la aplicación de temas Gtk y seleccionar el tema “Nodoka-Midnight”. Parece ser el tema que mejor integra el modo oscuro en Pidgin.
• Ir a tu carpeta personal y buscar el archivo “.gtkrc-2.0” (tendrás que mostrar los archivos ocultos para encontrarlo. Recuerda una vez copiado, quitar el punto en el nombre para que aplique bien el tema a Pidgin, dejando el nombre así «gtkrc-2.0».
• Copiar ese archivo a la carpeta “.purple” que es donde está todo lo relacionado con Pidgin.
• Reiniciar, y después abrir Pidgin normalmente. Ya debería verse con el tema oscuro.
• Unas capturas de pantalla:

Anteriormente habíamos instalado un tema ampliado de emojis, para activarlo hay que ir a preferencias en el apartado “Temas > Tema de emoticonos” y seleccionar el tema aparecera como Whatsapp/iOS Emojis.

Extra de accesos, atajos otros.

• Desde la ventana principal con “Ctrl+f” podemos buscar un chat. Si tenemos por ejemplo un nombre igual en dos cuentas distintas (Whatsapp y Telegram) Pidgin informará de qué cuenta queremos el chat.
• Desde la ventana de un chat “Ctrl+f” para buscar en el chat en el que estamos.
• Desde la ventana de chats “Ctr+m” para abrir un chat nuevo o buscar uno para abrir conversación.
• Desde el menú “Conversación > Ver historial” tenemos el historial del chat en el que estemos (recuerda marcar antes el plugin “Histórico” desde la sección de complementos).
• Desde la ventana principal “Lista de amigos”, “Ctrl-p” para abrir preferencias.

Complementos

• Histórico: Muestra las conversaciones previas del chat. Introduce la última conversación antes del inicio de la nueva.
• Libnotify Popus (ojo no confundir con Libnotify+): Muestra avisos mediante libnotify
• Notificación de mensajes: Permite notificar la presencia de mensajes no leídos.
• Nueva línea: Añade una línea horizontal para separar las conversaciones antiguas de las nuevas.
• Window-merge: es un complemento que permite unir la ventana «amigos» y la ventana «chats».

Puedes configurar estos complementos desde la opción «Configurar complemento» justo más abajo de la ventana.

Esperamos que te haya interesado este tutorial, para configurar y usar una aplicación que aunque no es muy conocida, es una joya para gestionar mensajería desde el pc con mínimos recursos, y lo mejor de todo, desde los repos de Mageia y BlogDrake!!!.

Publication date: 04 Aug 2026
Type: security
Affected Mageia releases : 9
CVE: CVE-2026-7260 , CVE-2026-17543 Description This update brings the latest version of php 8.2 and fixes some security vulnerabilities. References

• https://bugs.mageia.org/show_bug.cgi?id=36034
• https://www.php.net/ChangeLog-8.php#8.2.33
• https://www.cve.org/CVERecord?id=CVE-2026-7260
• https://www.cve.org/CVERecord?id=CVE-2026-17543

SRPMS 9/core

• php-8.2.33-1.mga9

Publication date: 04 Aug 2026
Type: security
Affected Mageia releases : 10 , 9
CVE: CVE-2026-54369 , CVE-2026-54370 , CVE-2026-54371 Description The updated acl and attr packages fix security issues. References

• https://bugs.mageia.org/show_bug.cgi?id=35779
• https://www.openwall.com/lists/oss-security/2026/06/29/1
• https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3TDUECPBS6YQPFZZ6RNXV3T5EFLLHQZS/
• https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/CGDSXLCG4AXTWFBAKM6XYUUYO6LZ7YXY/
• https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/message/NOOHLEV27XADU2EMOLPK2E6IY2TZKFKQ/
• https://www.cve.org/CVERecord?id=CVE-2026-54369
• https://www.cve.org/CVERecord?id=CVE-2026-54370
• https://www.cve.org/CVERecord?id=CVE-2026-54371

SRPMS 10/core

• acl-2.4.0-3.mga10
• attr-2.6.0-1.mga10

9/core

• acl-2.4.0-1.mga9
• attr-2.6.0-1.mga9

Publication date: 03 Aug 2026
Type: security
Affected Mageia releases : 10 , 9
CVE: CVE-2026-8594 Description The updated package fixes a security vulnerability: Text::LineFold versions through 2019.001 for Perl duplicate the output based on the number of special break characters. (CVE-2026-8594) References

• https://bugs.mageia.org/show_bug.cgi?id=35612
• https://www.openwall.com/lists/oss-security/2026/05/30/6
• https://www.cve.org/CVERecord?id=CVE-2026-8594

SRPMS 10/core

• perl-Unicode-LineBreak-2019.1.0-13.1.mga10

9/core

• perl-Unicode-LineBreak-2019.1.0-9.1.mga9

Publication date: 03 Aug 2026
Type: security
Affected Mageia releases : 10
CVE: CVE-2026-47729 , CVE-2026-50012 Description The updated packages fix security vulnerabilities: Due to a Improper Validation of Syntactic Correctness of Inputbug, Squid is vulnerable to a Out-of-bounds Read attack against the FTP gateway. (CVE-2026-47729) Due to an Improper Input Validation bug, Squid is vulnerable to a Heap-based Buffer Overflow attack against cache digests. (CVE-2026-50012) References

• https://bugs.mageia.org/show_bug.cgi?id=35686
• https://www.openwall.com/lists/oss-security/2026/06/12/1
• https://ubuntu.com/security/notices/USN-8435-1
• https://lists.debian.org/debian-security-announce/2026/msg00271.html
• https://www.cve.org/CVERecord?id=CVE-2026-47729
• https://www.cve.org/CVERecord?id=CVE-2026-50012

SRPMS 10/core

• squid-6.12-3.1.mga10

Publication date: 03 Aug 2026
Type: security
Affected Mageia releases : 10 , 9
CVE: CVE-2026-11526 Description The updated package fixes a security vulnerability: GD versions before 2.86 for Perl allow OS command injection and file overwrite via a 2-arg open() of filename arguments in _make_filehandle. (CVE-2026-11526) References

• https://bugs.mageia.org/show_bug.cgi?id=35700
• https://www.openwall.com/lists/oss-security/2026/06/14/4
• https://metacpan.org/release/RURBAN/GD-2.86/changes
• https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/message/FVXC7OE25PPTJFDV7ZFH2DDNTN5ZOZKK/
• https://lists.debian.org/debian-security-announce/2026/msg00256.html
• https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WWKANNR4XL34RWTURYNNLPBPFQSJWY4H/
• https://ubuntu.com/security/notices/USN-8484-1
• https://www.cve.org/CVERecord?id=CVE-2026-11526

SRPMS 10/core

• perl-GD-2.840.0-1.1.mga10

9/core

• perl-GD-2.760.0-3.1.mga9

Publication date: 03 Aug 2026
Type: security
Affected Mageia releases : 10 , 9
CVE: CVE-2026-13221 , CVE-2026-57432 , CVE-2026-57433 Description The updated Mageia 10 perl packages contain security fixes for CVE-2026-13221, CVE-2026-57432 and CVE-2026-57433. The Mageia 9 perl packages were not affected by CVE-2026-13221, they are now updated with fixes for CVE-2026-57432 and CVE-2026-57433. References

• https://bugs.mageia.org/show_bug.cgi?id=35925
• https://www.openwall.com/lists/oss-security/2026/07/13/5
• https://www.openwall.com/lists/oss-security/2026/07/13/6
• https://www.openwall.com/lists/oss-security/2026/07/13/7
• https://www.cve.org/CVERecord?id=CVE-2026-13221
• https://www.cve.org/CVERecord?id=CVE-2026-57432
• https://www.cve.org/CVERecord?id=CVE-2026-57433

SRPMS 10/core

• perl-5.42.0-3.mga10

9/core

• perl-5.36.0-1.4.mga9

Publication date: 03 Aug 2026
Type: security
Affected Mageia releases : 10 , 9
CVE: CVE-2026-14586 , CVE-2026-32665 , CVE-2026-40691 , CVE-2026-41637 , CVE-2026-42955 , CVE-2026-44621 , CVE-2026-44687 , CVE-2026-44690 , CVE-2026-46582 , CVE-2026-50045 , CVE-2026-50046 , CVE-2026-50243 , CVE-2026-50248 , CVE-2026-50251 , CVE-2026-50252 , CVE-2026-52863 , CVE-2026-54478 , CVE-2026-55708 , CVE-2026-55717 , CVE-2026-55973 , CVE-2026-55990 , CVE-2026-55991 , CVE-2026-56416 , CVE-2026-56444 Description Unbound packages updated to version 1.25.2 which incorporates a number of security and bug fixes. References

• https://bugs.mageia.org/show_bug.cgi?id=35991
• https://community.nlnetlabs.nl/t/unbound-1-25-2-released/3430
• https://www.openwall.com/lists/oss-security/2026/07/22/7
• https://nlnetlabs.nl/projects/unbound/security-advisories/
• https://www.cve.org/CVERecord?id=CVE-2026-14586
• https://www.cve.org/CVERecord?id=CVE-2026-32665
• https://www.cve.org/CVERecord?id=CVE-2026-40691
• https://www.cve.org/CVERecord?id=CVE-2026-41637
• https://www.cve.org/CVERecord?id=CVE-2026-42955
• https://www.cve.org/CVERecord?id=CVE-2026-44621
• https://www.cve.org/CVERecord?id=CVE-2026-44687
• https://www.cve.org/CVERecord?id=CVE-2026-44690
• https://www.cve.org/CVERecord?id=CVE-2026-46582
• https://www.cve.org/CVERecord?id=CVE-2026-50045
• https://www.cve.org/CVERecord?id=CVE-2026-50046
• https://www.cve.org/CVERecord?id=CVE-2026-50243
• https://www.cve.org/CVERecord?id=CVE-2026-50248
• https://www.cve.org/CVERecord?id=CVE-2026-50251
• https://www.cve.org/CVERecord?id=CVE-2026-50252
• https://www.cve.org/CVERecord?id=CVE-2026-52863
• https://www.cve.org/CVERecord?id=CVE-2026-54478
• https://www.cve.org/CVERecord?id=CVE-2026-55708
• https://www.cve.org/CVERecord?id=CVE-2026-55717
• https://www.cve.org/CVERecord?id=CVE-2026-55973
• https://www.cve.org/CVERecord?id=CVE-2026-55990
• https://www.cve.org/CVERecord?id=CVE-2026-55991
• https://www.cve.org/CVERecord?id=CVE-2026-56416
• https://www.cve.org/CVERecord?id=CVE-2026-56444

SRPMS 10/core

• unbound-1.25.2-1.mga10

9/core

• unbound-1.25.2-1.mga9

Publication date: 03 Aug 2026
Type: security
Affected Mageia releases : 10 , 9
CVE: CVE-2026-32853 , CVE-2026-32854 , CVE-2026-44988 , CVE-2026-50538 Description The updated packages fix security vulnerabilities: Heap Out-of-Bounds Read in HandleUltraZipBPP due to unchecked subrectangle count. (CVE-2026-32853) NULL pointer dereferences in httpd proxy handlers via malformed CONNECT/GET requests. (CVE-2026-32854) LibVNCClient Tight Gradient decoding allows malicious server-triggered heap/stack OOB writes. (CVE-2026-44988) Attacker-controlled heap out-of-bounds write in libvncclient Tight decoder. (CVE-2026-50538) References

• https://bugs.mageia.org/show_bug.cgi?id=35628
• https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/message/SULCQANWMHMI72ZJZEJWSA2YD3ZSRUKQ/
• https://github.com/LibVNC/libvncserver/security/advisories/GHSA-jcc5-8wj4-7c58
• https://ubuntu.com/security/notices/USN-8463-1
• https://github.com/LibVNC/libvncserver/security/advisories/GHSA-87q7-v983-qwcj
• https://github.com/LibVNC/libvncserver/security/advisories/GHSA-xjp8-4qqv-5x4x
• https://ubuntu.com/security/notices/USN-8494-1
• https://github.com/LibVNC/libvncserver/security/advisories/GHSA-v9pm-47h4-jcq8
• https://www.cve.org/CVERecord?id=CVE-2026-32853
• https://www.cve.org/CVERecord?id=CVE-2026-32854
• https://www.cve.org/CVERecord?id=CVE-2026-44988
• https://www.cve.org/CVERecord?id=CVE-2026-50538

SRPMS 10/core

• libvncserver-0.9.15-2.1.mga10

9/core

• libvncserver-0.9.14-1.1.mga9

Publication date: 03 Aug 2026
Type: security
Affected Mageia releases : 10 , 9
CVE: CVE-2023-35789 , CVE-2026-44235 , CVE-2026-44236 Description The updated packages fix security vulnerabilities: An issue was discovered in the C AMQP client library (aka rabbitmq-c) through 0.13.0 for RabbitMQ. Credentials can only be entered on the command line (e.g., for amqp-publish or amqp-consume) and are thus visible to local attackers by listing a process and its arguments. (CVE-2023-35789) size_t underflow in AMQP frame length computation leads to out-of-bounds read in rabbitmq-c. (CVE-2026-44235) Heap buffer overflow in AMQP login handshake via undersized connection.tune.frame_max. (CVE-2026-44236) References

• https://bugs.mageia.org/show_bug.cgi?id=35702
• https://lists.debian.org/debian-security-announce/2026/msg00254.html
• https://github.com/alanxz/rabbitmq-c/security/advisories/GHSA-9mmv-r8g3-qp46
• https://github.com/alanxz/rabbitmq-c/security/advisories/GHSA-jh48-qjf5-fx5v
• https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/RVOR7C3KDMOVLKB4FNMSD3YNXP3MG4YD/
• https://ubuntu.com/security/notices/USN-8437-1
• https://www.cve.org/CVERecord?id=CVE-2023-35789
• https://www.cve.org/CVERecord?id=CVE-2026-44235
• https://www.cve.org/CVERecord?id=CVE-2026-44236

SRPMS 10/core

• librabbitmq-0.15.0-2.1.mga10

9/core

• librabbitmq-0.11.0-1.1.mga9

Publication date: 03 Aug 2026
Type: security
Affected Mageia releases : 10 , 9
CVE: CVE-2026-35091 , CVE-2026-35092 Description The updated packages fix security vulnerabilities: Denial of service and information disclosure via crafted udp packet. (CVE-2026-35091) Denial of service via integer overflow in join message validation. (CVE-2026-35092) Additionally, libqb solves a missing runtime dependency on qb-blackbox. References

• https://bugs.mageia.org/show_bug.cgi?id=35431
• https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/XTKM7OVSXAWVNF3FJR76YF55O7VHHZJ7/
• https://lists.debian.org/debian-security-announce/2026/msg00172.html
• https://www.cve.org/CVERecord?id=CVE-2026-35091
• https://www.cve.org/CVERecord?id=CVE-2026-35092

SRPMS 10/core

• corosync-3.1.10-2.1.mga10
• libqb-2.0.9-1.1.mga10

9/core

• corosync-3.1.7-1.3.mga9
• libqb-2.0.8-1.1.mga9

Publication date: 01 Aug 2026
Type: security
Affected Mageia releases : 10
CVE: CVE-2026-52908 , CVE-2026-52909 , CVE-2026-52910 , CVE-2026-52917 , CVE-2026-52924 , CVE-2026-52929 , CVE-2026-52930 , CVE-2026-52935 , CVE-2026-52939 , CVE-2026-52940 , CVE-2026-52942 , CVE-2026-52946 , CVE-2026-52947 , CVE-2026-52948 , CVE-2026-53131 , CVE-2026-53132 , CVE-2026-53133 , CVE-2026-53134 , CVE-2026-53135 , CVE-2026-53136 , CVE-2026-53137 , CVE-2026-53138 , CVE-2026-53139 , CVE-2026-53140 , CVE-2026-53141 , CVE-2026-53142 , CVE-2026-53143 , CVE-2026-53144 , CVE-2026-53145 , CVE-2026-53146 , CVE-2026-53147 , CVE-2026-53148 , CVE-2026-53149 , CVE-2026-53150 , CVE-2026-53151 , CVE-2026-53152 , CVE-2026-53153 , CVE-2026-53154 , CVE-2026-53156 , CVE-2026-53157 , CVE-2026-53158 , CVE-2026-53159 , CVE-2026-53160 , CVE-2026-53161 , CVE-2026-53162 , CVE-2026-53163 , CVE-2026-53164 , CVE-2026-53166 , CVE-2026-53167 , CVE-2026-53168 , CVE-2026-53175 , CVE-2026-53176 , CVE-2026-53177 , CVE-2026-53179 , CVE-2026-53180 , CVE-2026-53181 , CVE-2026-53182 , CVE-2026-53183 , CVE-2026-53184 , CVE-2026-53185 , CVE-2026-53186 , CVE-2026-53187 , CVE-2026-53188 , CVE-2026-53189 , CVE-2026-53190 , CVE-2026-53191 , CVE-2026-53192 , CVE-2026-53193 , CVE-2026-53194 , CVE-2026-53195 , CVE-2026-53196 , CVE-2026-53197 , CVE-2026-53198 , CVE-2026-53199 , CVE-2026-53202 , CVE-2026-53203 , CVE-2026-53205 , CVE-2026-53207 , CVE-2026-53208 , CVE-2026-53209 , CVE-2026-53210 , CVE-2026-53211 , CVE-2026-53212 , CVE-2026-53213 , CVE-2026-53214 , CVE-2026-53215 , CVE-2026-53216 , CVE-2026-53217 , CVE-2026-53218 , CVE-2026-53219 , CVE-2026-53220 , CVE-2026-53221 , CVE-2026-53223 , CVE-2026-53224 , CVE-2026-53225 , CVE-2026-53226 , CVE-2026-53227 , CVE-2026-53228 , CVE-2026-53229 , CVE-2026-53230 , CVE-2026-53233 , CVE-2026-53234 , CVE-2026-53235 , CVE-2026-53236 , CVE-2026-53237 , CVE-2026-53238 , CVE-2026-53239 , CVE-2026-53240 , CVE-2026-53241 , CVE-2026-53242 , CVE-2026-53245 , CVE-2026-53246 , CVE-2026-53247 , CVE-2026-53248 , CVE-2026-53249 , CVE-2026-53250 , CVE-2026-53251 , CVE-2026-53252 , CVE-2026-53253 , CVE-2026-53254 , CVE-2026-53255 , CVE-2026-53256 , CVE-2026-53258 , CVE-2026-53259 , CVE-2026-53261 , CVE-2026-53262 , CVE-2026-53263 , CVE-2026-53264 , CVE-2026-53265 , CVE-2026-53266 , CVE-2026-53267 , CVE-2026-53268 , CVE-2026-53269 , CVE-2026-53270 , CVE-2026-53271 , CVE-2026-53272 , CVE-2026-53273 , CVE-2026-53274 , CVE-2026-53275 , CVE-2026-53277 , CVE-2026-53325 , CVE-2026-53327 , CVE-2026-53328 , CVE-2026-53329 , CVE-2026-53330 , CVE-2026-53331 , CVE-2026-53332 , CVE-2026-53333 , CVE-2026-53334 , CVE-2026-53335 , CVE-2026-53336 , CVE-2026-53337 , CVE-2026-53338 , CVE-2026-53339 , CVE-2026-53340 , CVE-2026-53341 , CVE-2026-53342 , CVE-2026-53343 , CVE-2026-53345 , CVE-2026-53346 , CVE-2026-53347 , CVE-2026-53349 , CVE-2026-53350 , CVE-2026-53352 , CVE-2026-53353 , CVE-2026-53354 , CVE-2026-53355 , CVE-2026-53356 , CVE-2026-53359 , CVE-2026-53361 , CVE-2026-53362 , CVE-2026-53363 , CVE-2026-53366 , CVE-2026-53381 , CVE-2026-53382 , CVE-2026-53383 , CVE-2026-53384 , CVE-2026-53385 , CVE-2026-53386 , CVE-2026-53387 , CVE-2026-53388 , CVE-2026-53389 , CVE-2026-53390 , CVE-2026-53391 , CVE-2026-53392 , CVE-2026-53393 , CVE-2026-53394 , CVE-2026-53397 , CVE-2026-53398 , CVE-2026-53399 , CVE-2026-53400 , CVE-2026-53402 , CVE-2026-53403 , CVE-2026-63794 , CVE-2026-63795 , CVE-2026-63796 , CVE-2026-63797 , CVE-2026-63798 , CVE-2026-63800 , CVE-2026-63801 , CVE-2026-63802 , CVE-2026-63803 , CVE-2026-63804 , CVE-2026-63805 , CVE-2026-63806 , CVE-2026-63807 , CVE-2026-63808 , CVE-2026-63809 , CVE-2026-63810 , CVE-2026-63812 , CVE-2026-63814 , CVE-2026-63815 , CVE-2026-63816 , CVE-2026-63817 , CVE-2026-63818 , CVE-2026-63819 , CVE-2026-63821 , CVE-2026-63822 , CVE-2026-63823 , CVE-2026-63824 , CVE-2026-63825 , CVE-2026-63826 , CVE-2026-63827 , CVE-2026-63828 , CVE-2026-63829 , CVE-2026-63830 , CVE-2026-63831 , CVE-2026-63832 , CVE-2026-63833 , CVE-2026-63834 , CVE-2026-63835 , CVE-2026-63836 , CVE-2026-63867 , CVE-2026-63868 , CVE-2026-63869 , CVE-2026-63870 , CVE-2026-63871 , CVE-2026-63873 , CVE-2026-63874 , CVE-2026-64187 , CVE-2026-64188 , CVE-2026-64189 , CVE-2026-64191 , CVE-2026-64205 , CVE-2026-64206 , CVE-2026-64207 Description Upstream kernel version 6.18.39 fixes bugs and vulnerabilities. The kmod, bluez, wireless-regdb, firmware and drakx-installer-images packages have been updated to work with this new kernel. References

• https://bugs.mageia.org/show_bug.cgi?id=35976
• https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.18.36
• https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.18.37
• https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.18.38
• https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.18.39
• https://www.cve.org/CVERecord?id=CVE-2026-52908
• https://www.cve.org/CVERecord?id=CVE-2026-52909
• https://www.cve.org/CVERecord?id=CVE-2026-52910
• https://www.cve.org/CVERecord?id=CVE-2026-52917
• https://www.cve.org/CVERecord?id=CVE-2026-52924
• https://www.cve.org/CVERecord?id=CVE-2026-52929
• https://www.cve.org/CVERecord?id=CVE-2026-52930
• https://www.cve.org/CVERecord?id=CVE-2026-52935
• https://www.cve.org/CVERecord?id=CVE-2026-52939
• https://www.cve.org/CVERecord?id=CVE-2026-52940
• https://www.cve.org/CVERecord?id=CVE-2026-52942
• https://www.cve.org/CVERecord?id=CVE-2026-52946
• https://www.cve.org/CVERecord?id=CVE-2026-52947
• https://www.cve.org/CVERecord?id=CVE-2026-52948
• https://www.cve.org/CVERecord?id=CVE-2026-53131
• https://www.cve.org/CVERecord?id=CVE-2026-53132
• https://www.cve.org/CVERecord?id=CVE-2026-53133
• https://www.cve.org/CVERecord?id=CVE-2026-53134
• https://www.cve.org/CVERecord?id=CVE-2026-53135
• https://www.cve.org/CVERecord?id=CVE-2026-53136
• https://www.cve.org/CVERecord?id=CVE-2026-53137
• https://www.cve.org/CVERecord?id=CVE-2026-53138
• https://www.cve.org/CVERecord?id=CVE-2026-53139
• https://www.cve.org/CVERecord?id=CVE-2026-53140
• https://www.cve.org/CVERecord?id=CVE-2026-53141
• https://www.cve.org/CVERecord?id=CVE-2026-53142
• https://www.cve.org/CVERecord?id=CVE-2026-53143
• https://www.cve.org/CVERecord?id=CVE-2026-53144
• https://www.cve.org/CVERecord?id=CVE-2026-53145
• https://www.cve.org/CVERecord?id=CVE-2026-53146
• https://www.cve.org/CVERecord?id=CVE-2026-53147
• https://www.cve.org/CVERecord?id=CVE-2026-53148
• https://www.cve.org/CVERecord?id=CVE-2026-53149
• https://www.cve.org/CVERecord?id=CVE-2026-53150
• https://www.cve.org/CVERecord?id=CVE-2026-53151
• https://www.cve.org/CVERecord?id=CVE-2026-53152
• https://www.cve.org/CVERecord?id=CVE-2026-53153
• https://www.cve.org/CVERecord?id=CVE-2026-53154
• https://www.cve.org/CVERecord?id=CVE-2026-53156
• https://www.cve.org/CVERecord?id=CVE-2026-53157
• https://www.cve.org/CVERecord?id=CVE-2026-53158
• https://www.cve.org/CVERecord?id=CVE-2026-53159
• https://www.cve.org/CVERecord?id=CVE-2026-53160
• https://www.cve.org/CVERecord?id=CVE-2026-53161
• https://www.cve.org/CVERecord?id=CVE-2026-53162
• https://www.cve.org/CVERecord?id=CVE-2026-53163
• https://www.cve.org/CVERecord?id=CVE-2026-53164
• https://www.cve.org/CVERecord?id=CVE-2026-53166
• https://www.cve.org/CVERecord?id=CVE-2026-53167
• https://www.cve.org/CVERecord?id=CVE-2026-53168
• https://www.cve.org/CVERecord?id=CVE-2026-53175
• https://www.cve.org/CVERecord?id=CVE-2026-53176
• https://www.cve.org/CVERecord?id=CVE-2026-53177
• https://www.cve.org/CVERecord?id=CVE-2026-53179
• https://www.cve.org/CVERecord?id=CVE-2026-53180
• https://www.cve.org/CVERecord?id=CVE-2026-53181
• https://www.cve.org/CVERecord?id=CVE-2026-53182
• https://www.cve.org/CVERecord?id=CVE-2026-53183
• https://www.cve.org/CVERecord?id=CVE-2026-53184
• https://www.cve.org/CVERecord?id=CVE-2026-53185
• https://www.cve.org/CVERecord?id=CVE-2026-53186
• https://www.cve.org/CVERecord?id=CVE-2026-53187
• https://www.cve.org/CVERecord?id=CVE-2026-53188
• https://www.cve.org/CVERecord?id=CVE-2026-53189
• https://www.cve.org/CVERecord?id=CVE-2026-53190
• https://www.cve.org/CVERecord?id=CVE-2026-53191
• https://www.cve.org/CVERecord?id=CVE-2026-53192
• https://www.cve.org/CVERecord?id=CVE-2026-53193
• https://www.cve.org/CVERecord?id=CVE-2026-53194
• https://www.cve.org/CVERecord?id=CVE-2026-53195
• https://www.cve.org/CVERecord?id=CVE-2026-53196
• https://www.cve.org/CVERecord?id=CVE-2026-53197
• https://www.cve.org/CVERecord?id=CVE-2026-53198
• https://www.cve.org/CVERecord?id=CVE-2026-53199
• https://www.cve.org/CVERecord?id=CVE-2026-53202
• https://www.cve.org/CVERecord?id=CVE-2026-53203
• https://www.cve.org/CVERecord?id=CVE-2026-53205
• https://www.cve.org/CVERecord?id=CVE-2026-53207
• https://www.cve.org/CVERecord?id=CVE-2026-53208
• https://www.cve.org/CVERecord?id=CVE-2026-53209
• https://www.cve.org/CVERecord?id=CVE-2026-53210
• https://www.cve.org/CVERecord?id=CVE-2026-53211
• https://www.cve.org/CVERecord?id=CVE-2026-53212
• https://www.cve.org/CVERecord?id=CVE-2026-53213
• https://www.cve.org/CVERecord?id=CVE-2026-53214
• https://www.cve.org/CVERecord?id=CVE-2026-53215
• https://www.cve.org/CVERecord?id=CVE-2026-53216
• https://www.cve.org/CVERecord?id=CVE-2026-53217
• https://www.cve.org/CVERecord?id=CVE-2026-53218
• https://www.cve.org/CVERecord?id=CVE-2026-53219
• https://www.cve.org/CVERecord?id=CVE-2026-53220
• https://www.cve.org/CVERecord?id=CVE-2026-53221
• https://www.cve.org/CVERecord?id=CVE-2026-53223
• https://www.cve.org/CVERecord?id=CVE-2026-53224
• https://www.cve.org/CVERecord?id=CVE-2026-53225
• https://www.cve.org/CVERecord?id=CVE-2026-53226
• https://www.cve.org/CVERecord?id=CVE-2026-53227
• https://www.cve.org/CVERecord?id=CVE-2026-53228
• https://www.cve.org/CVERecord?id=CVE-2026-53229
• https://www.cve.org/CVERecord?id=CVE-2026-53230
• https://www.cve.org/CVERecord?id=CVE-2026-53233
• https://www.cve.org/CVERecord?id=CVE-2026-53234
• https://www.cve.org/CVERecord?id=CVE-2026-53235
• https://www.cve.org/CVERecord?id=CVE-2026-53236
• https://www.cve.org/CVERecord?id=CVE-2026-53237
• https://www.cve.org/CVERecord?id=CVE-2026-53238
• https://www.cve.org/CVERecord?id=CVE-2026-53239
• https://www.cve.org/CVERecord?id=CVE-2026-53240
• https://www.cve.org/CVERecord?id=CVE-2026-53241
• https://www.cve.org/CVERecord?id=CVE-2026-53242
• https://www.cve.org/CVERecord?id=CVE-2026-53245
• https://www.cve.org/CVERecord?id=CVE-2026-53246
• https://www.cve.org/CVERecord?id=CVE-2026-53247
• https://www.cve.org/CVERecord?id=CVE-2026-53248
• https://www.cve.org/CVERecord?id=CVE-2026-53249
• https://www.cve.org/CVERecord?id=CVE-2026-53250
• https://www.cve.org/CVERecord?id=CVE-2026-53251
• https://www.cve.org/CVERecord?id=CVE-2026-53252
• https://www.cve.org/CVERecord?id=CVE-2026-53253
• https://www.cve.org/CVERecord?id=CVE-2026-53254
• https://www.cve.org/CVERecord?id=CVE-2026-53255
• https://www.cve.org/CVERecord?id=CVE-2026-53256
• https://www.cve.org/CVERecord?id=CVE-2026-53258
• https://www.cve.org/CVERecord?id=CVE-2026-53259
• https://www.cve.org/CVERecord?id=CVE-2026-53261
• https://www.cve.org/CVERecord?id=CVE-2026-53262
• https://www.cve.org/CVERecord?id=CVE-2026-53263
• https://www.cve.org/CVERecord?id=CVE-2026-53264
• https://www.cve.org/CVERecord?id=CVE-2026-53265
• https://www.cve.org/CVERecord?id=CVE-2026-53266
• https://www.cve.org/CVERecord?id=CVE-2026-53267
• https://www.cve.org/CVERecord?id=CVE-2026-53268
• https://www.cve.org/CVERecord?id=CVE-2026-53269
• https://www.cve.org/CVERecord?id=CVE-2026-53270
• https://www.cve.org/CVERecord?id=CVE-2026-53271
• https://www.cve.org/CVERecord?id=CVE-2026-53272
• https://www.cve.org/CVERecord?id=CVE-2026-53273
• https://www.cve.org/CVERecord?id=CVE-2026-53274
• https://www.cve.org/CVERecord?id=CVE-2026-53275
• https://www.cve.org/CVERecord?id=CVE-2026-53277
• https://www.cve.org/CVERecord?id=CVE-2026-53325
• https://www.cve.org/CVERecord?id=CVE-2026-53327
• https://www.cve.org/CVERecord?id=CVE-2026-53328
• https://www.cve.org/CVERecord?id=CVE-2026-53329
• https://www.cve.org/CVERecord?id=CVE-2026-53330
• https://www.cve.org/CVERecord?id=CVE-2026-53331
• https://www.cve.org/CVERecord?id=CVE-2026-53332
• https://www.cve.org/CVERecord?id=CVE-2026-53333
• https://www.cve.org/CVERecord?id=CVE-2026-53334
• https://www.cve.org/CVERecord?id=CVE-2026-53335
• https://www.cve.org/CVERecord?id=CVE-2026-53336
• https://www.cve.org/CVERecord?id=CVE-2026-53337
• https://www.cve.org/CVERecord?id=CVE-2026-53338
• https://www.cve.org/CVERecord?id=CVE-2026-53339
• https://www.cve.org/CVERecord?id=CVE-2026-53340
• https://www.cve.org/CVERecord?id=CVE-2026-53341
• https://www.cve.org/CVERecord?id=CVE-2026-53342
• https://www.cve.org/CVERecord?id=CVE-2026-53343
• https://www.cve.org/CVERecord?id=CVE-2026-53345
• https://www.cve.org/CVERecord?id=CVE-2026-53346
• https://www.cve.org/CVERecord?id=CVE-2026-53347
• https://www.cve.org/CVERecord?id=CVE-2026-53349
• https://www.cve.org/CVERecord?id=CVE-2026-53350
• https://www.cve.org/CVERecord?id=CVE-2026-53352
• https://www.cve.org/CVERecord?id=CVE-2026-53353
• https://www.cve.org/CVERecord?id=CVE-2026-53354
• https://www.cve.org/CVERecord?id=CVE-2026-53355
• https://www.cve.org/CVERecord?id=CVE-2026-53356
• https://www.cve.org/CVERecord?id=CVE-2026-53359
• https://www.cve.org/CVERecord?id=CVE-2026-53361
• https://www.cve.org/CVERecord?id=CVE-2026-53362
• https://www.cve.org/CVERecord?id=CVE-2026-53363
• https://www.cve.org/CVERecord?id=CVE-2026-53366
• https://www.cve.org/CVERecord?id=CVE-2026-53381
• https://www.cve.org/CVERecord?id=CVE-2026-53382
• https://www.cve.org/CVERecord?id=CVE-2026-53383
• https://www.cve.org/CVERecord?id=CVE-2026-53384
• https://www.cve.org/CVERecord?id=CVE-2026-53385
• https://www.cve.org/CVERecord?id=CVE-2026-53386
• https://www.cve.org/CVERecord?id=CVE-2026-53387
• https://www.cve.org/CVERecord?id=CVE-2026-53388
• https://www.cve.org/CVERecord?id=CVE-2026-53389
• https://www.cve.org/CVERecord?id=CVE-2026-53390
• https://www.cve.org/CVERecord?id=CVE-2026-53391
• https://www.cve.org/CVERecord?id=CVE-2026-53392
• https://www.cve.org/CVERecord?id=CVE-2026-53393
• https://www.cve.org/CVERecord?id=CVE-2026-53394
• https://www.cve.org/CVERecord?id=CVE-2026-53397
• https://www.cve.org/CVERecord?id=CVE-2026-53398
• https://www.cve.org/CVERecord?id=CVE-2026-53399
• https://www.cve.org/CVERecord?id=CVE-2026-53400
• https://www.cve.org/CVERecord?id=CVE-2026-53402
• https://www.cve.org/CVERecord?id=CVE-2026-53403
• https://www.cve.org/CVERecord?id=CVE-2026-63794
• https://www.cve.org/CVERecord?id=CVE-2026-63795
• https://www.cve.org/CVERecord?id=CVE-2026-63796
• https://www.cve.org/CVERecord?id=CVE-2026-63797
• https://www.cve.org/CVERecord?id=CVE-2026-63798
• https://www.cve.org/CVERecord?id=CVE-2026-63800
• https://www.cve.org/CVERecord?id=CVE-2026-63801
• https://www.cve.org/CVERecord?id=CVE-2026-63802
• https://www.cve.org/CVERecord?id=CVE-2026-63803
• https://www.cve.org/CVERecord?id=CVE-2026-63804
• https://www.cve.org/CVERecord?id=CVE-2026-63805
• https://www.cve.org/CVERecord?id=CVE-2026-63806
• https://www.cve.org/CVERecord?id=CVE-2026-63807
• https://www.cve.org/CVERecord?id=CVE-2026-63808
• https://www.cve.org/CVERecord?id=CVE-2026-63809
• https://www.cve.org/CVERecord?id=CVE-2026-63810
• https://www.cve.org/CVERecord?id=CVE-2026-63812
• https://www.cve.org/CVERecord?id=CVE-2026-63814
• https://www.cve.org/CVERecord?id=CVE-2026-63815
• https://www.cve.org/CVERecord?id=CVE-2026-63816
• https://www.cve.org/CVERecord?id=CVE-2026-63817
• https://www.cve.org/CVERecord?id=CVE-2026-63818
• https://www.cve.org/CVERecord?id=CVE-2026-63819
• https://www.cve.org/CVERecord?id=CVE-2026-63821
• https://www.cve.org/CVERecord?id=CVE-2026-63822
• https://www.cve.org/CVERecord?id=CVE-2026-63823
• https://www.cve.org/CVERecord?id=CVE-2026-63824
• https://www.cve.org/CVERecord?id=CVE-2026-63825
• https://www.cve.org/CVERecord?id=CVE-2026-63826
• https://www.cve.org/CVERecord?id=CVE-2026-63827
• https://www.cve.org/CVERecord?id=CVE-2026-63828
• https://www.cve.org/CVERecord?id=CVE-2026-63829
• https://www.cve.org/CVERecord?id=CVE-2026-63830
• https://www.cve.org/CVERecord?id=CVE-2026-63831
• https://www.cve.org/CVERecord?id=CVE-2026-63832
• https://www.cve.org/CVERecord?id=CVE-2026-63833
• https://www.cve.org/CVERecord?id=CVE-2026-63834
• https://www.cve.org/CVERecord?id=CVE-2026-63835
• https://www.cve.org/CVERecord?id=CVE-2026-63836
• https://www.cve.org/CVERecord?id=CVE-2026-63867
• https://www.cve.org/CVERecord?id=CVE-2026-63868
• https://www.cve.org/CVERecord?id=CVE-2026-63869
• https://www.cve.org/CVERecord?id=CVE-2026-63870
• https://www.cve.org/CVERecord?id=CVE-2026-63871
• https://www.cve.org/CVERecord?id=CVE-2026-63873
• https://www.cve.org/CVERecord?id=CVE-2026-63874
• https://www.cve.org/CVERecord?id=CVE-2026-64187
• https://www.cve.org/CVERecord?id=CVE-2026-64188
• https://www.cve.org/CVERecord?id=CVE-2026-64189
• https://www.cve.org/CVERecord?id=CVE-2026-64191
• https://www.cve.org/CVERecord?id=CVE-2026-64205
• https://www.cve.org/CVERecord?id=CVE-2026-64206
• https://www.cve.org/CVERecord?id=CVE-2026-64207

SRPMS 10/core

• kernel-6.18.39-1.mga10
• kmod-virtualbox-7.2.8-28.mga10
• kmod-xtables-addons-3.30-3.mga10
• bluez-5.87-1.mga10
• wireless-regdb-20260530-1.mga10
• kernel-firmware-20260622-1.mga10
• drakx-installer-images-2.94-54.mga10

10/nonfree

• kernel-firmware-nonfree-20260622-1.mga10.nonfree
• radeon-firmware-20260622-1.mga10.nonfree
• drakx-installer-images-2.94-54.mga10.nonfree
• kmod-nvidia-current-wopengpu-580.159.04-37.mga10.nonfree

Publication date: 30 Jul 2026
Type: security
Affected Mageia releases : 10 , 9
CVE: CVE-2026-56001 , CVE-2026-56002 , CVE-2026-56003 Description The updated packages fix security vulnerabilities: BitmapScaleBitmaps Integer Overflow Heap Buffer Overflow. (CVE-2026-56001) PCF Font Parsing Heap Buffer Overflow. (CVE-2026-56002) computeProps Property Buffer Heap Buffer Overflow. (CVE-2026-56003) References

• https://bugs.mageia.org/show_bug.cgi?id=35859
• https://www.openwall.com/lists/oss-security/2026/07/08/1
• https://www.cve.org/CVERecord?id=CVE-2026-56001
• https://www.cve.org/CVERecord?id=CVE-2026-56002
• https://www.cve.org/CVERecord?id=CVE-2026-56003

SRPMS 10/core

• libxfont2-2.0.8-1.mga10

9/core

• libxfont2-2.0.6-2.1.mga9

Publication date: 30 Jul 2026
Type: security
Affected Mageia releases : 10
CVE: CVE-2026-9064 Description The updated packages fix a security vulnerability: Unbounded ldap controls count in get_ldapmessage_controls_ext() causes cpu and heap amplification (remote dos). (CVE-2026-9064) References

• https://bugs.mageia.org/show_bug.cgi?id=35838
• https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/HGVVCWTZBWDJ7HSAGE646TODMKUK56FR/
• https://bugzilla.redhat.com/show_bug.cgi?id=2480093
• https://github.com/389ds/389-ds-base/issues/7503
• https://www.cve.org/CVERecord?id=CVE-2026-9064

SRPMS 10/core

• 389-ds-base-3.1.3-2.1.mga10

Publication date: 30 Jul 2026
Type: security
Affected Mageia releases : 10 , 9
CVE: CVE-2026-58055 Description The updated packages fix a security vulnerability: HTTP Request/Response Smuggling via Upgrade Request with Content-Length. (CVE-2026-58055) References

• https://bugs.mageia.org/show_bug.cgi?id=35814
• https://ubuntu.com/security/notices/USN-8495-1
• https://github.com/bikini/exploitarium/tree/main/nghttp2-nghttpx-upgrade-queue-poison-poc
• https://www.cve.org/CVERecord?id=CVE-2026-58055

SRPMS 10/core

• nghttp2-1.68.1-2.1.mga10

9/core

• nghttp2-1.61.0-1.2.mga9

Publication date: 30 Jul 2026
Type: security
Affected Mageia releases : 10 , 9
CVE: CVE-2026-9698 , CVE-2026-10879 , CVE-2026-14380 , CVE-2026-14739 , CVE-2026-14740 , CVE-2026-15043 , CVE-2026-15392 , CVE-2026-60081 , CVE-2026-60082 Description The updated packages fix several security issues. References

• https://bugs.mageia.org/show_bug.cgi?id=35643
• https://www.openwall.com/lists/oss-security/2026/06/06/4
• https://www.openwall.com/lists/oss-security/2026/06/09/9
• https://www.openwall.com/lists/oss-security/2026/07/07/16
• https://www.openwall.com/lists/oss-security/2026/07/07/17
• https://www.openwall.com/lists/oss-security/2026/07/14/9
• https://www.openwall.com/lists/oss-security/2026/07/14/13
• https://www.openwall.com/lists/oss-security/2026/07/14/14
• https://www.openwall.com/lists/oss-security/2026/07/14/15
• https://www.cve.org/CVERecord?id=CVE-2026-9698
• https://www.cve.org/CVERecord?id=CVE-2026-10879
• https://www.cve.org/CVERecord?id=CVE-2026-14380
• https://www.cve.org/CVERecord?id=CVE-2026-14739
• https://www.cve.org/CVERecord?id=CVE-2026-14740
• https://www.cve.org/CVERecord?id=CVE-2026-15043
• https://www.cve.org/CVERecord?id=CVE-2026-15392
• https://www.cve.org/CVERecord?id=CVE-2026-60081
• https://www.cve.org/CVERecord?id=CVE-2026-60082

SRPMS 10/core

• perl-DBI-1.651.0-1.mga10

9/core

• perl-DBI-1.651.0-1.mga9

Publication date: 28 Jul 2026
Type: security
Affected Mageia releases : 10
CVE: CVE-2026-52717 Description Heap corruption in gst-libav AV protocol pipe. (CVE-2026-52717) References

• https://bugs.mageia.org/show_bug.cgi?id=35738
• https://lists.debian.org/debian-security-announce/2026/msg00264.html
• https://gstreamer.freedesktop.org/security/sa-2026-0037.html
• https://www.cve.org/CVERecord?id=CVE-2026-52717

SRPMS 10/core

• gstreamer1.0-libav-1.26.11-1.1.mga10

Publication date: 28 Jul 2026
Type: security
Affected Mageia releases : 10 , 9
CVE: CVE-2026-9539 Description The updated packages fix a security vulnerability: TCP URG OOB Read Information Leak. (CVE-2026-9539) References

• https://bugs.mageia.org/show_bug.cgi?id=35786
• https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/message/6UPWKZGJYGWQEVDO5XRTPSVFGDX2BIZC/
• https://gitlab.freedesktop.org/slirp/libslirp/-/work_items/93
• https://www.cve.org/CVERecord?id=CVE-2026-9539

SRPMS 10/core

• libslirp-4.8.0-2.1.mga10

9/core

• libslirp-4.6.1-1.1.mga9