Critical Security Update for MariaDB: Addressing Multiple Vulnerabilities
Summary
ALSA-2026:0136: Important: mariadb10.11 security update. Affects mariadb versions < 3:10.11.15-1.el10_1. Fixed in 3:10.11.15-1.el10_1. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
MariaDB is a community-developed fork of MySQL, serving as a multi-user, multi-threaded SQL database server. It includes a server daemon (mariadbd) and various client programs and libraries. The package provides essential client programs and utilities for database management. However, recent vulnerabilities have been identified that could compromise the stability and security of MariaDB installations.
Vulnerability Detail
The vulnerabilities in MariaDB include a high privilege denial of service vulnerability (CVE-2025-21490), multiple crashes due to empty backtrace logs (CVE-2023-52969), and crashes via specific item references (CVE-2023-52970, CVE-2023-52971). Additionally, there are unspecified vulnerabilities in mysqldump and InnoDB (CVE-2025-30722, CVE-2025-30693), and a critical remote code execution vulnerability in the mariadb-dump utility due to improper path validation (CVE-2025-13699). These vulnerabilities can lead to service disruptions, data loss, and unauthorized access.
How To Fix
Minimum fixed version
3:10.11.15-1.el10_1
This is the first release that contains the fix.
sudo dnf update mariadbTip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
As a temporary workaround, consider disabling the affected services until the packages can be updated. This can be done using the following command:
sudo systemctl stop mariadb
Ensure to monitor the system for any unusual activity during this period.
Conclusion
In summary, the recent vulnerabilities in MariaDB pose significant risks to database security and stability. It is crucial to update to the patched version 3:10.11.15-1.el10_1 to mitigate these risks. Utilize tools like Vulert to monitor for vulnerabilities in your applications effectively.
See every vulnerability recorded for mariadb →
FAQ
The vulnerabilities can lead to service disruptions, crashes, and potential unauthorized access to the database.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by these vulnerabilities without needing to sign up.
If immediate updates are not possible, consider disabling the affected services as a temporary measure.
While specific exploits may not be publicly disclosed, the nature of the vulnerabilities suggests they could be exploited to cause service disruptions or unauthorized access.
Regularly check for updates and vulnerabilities, ideally on a weekly basis, to ensure your systems remain secure.
Related vulnerabilities
Recent vulnerabilities recorded for mariadb.
