MariaDB on Linux: which version fixes what

What it is, and why it is on your server

MariaDB is the default database on Debian and on Rocky and AlmaLinux, and the one most hosting panels install. Ubuntu stamps the branch into the source package name, so it is mariadb-10.6 on 22.04 and mariadb on 24.04.

Why its advisories behave the way they do

• Shared ancestry means shared bugs. When Oracle publishes a server flaw in code that predates the fork, MariaDB usually needs the same fix, and the two projects do not ship on the same day.
• It is what a panel installs. cPanel, Plesk and DirectAdmin overwhelmingly deploy MariaDB, which makes it the database actually running on most shared-hosting servers.
• Major versions are supported for years and then abruptly are not. A server sitting on a branch past its end-of-life date stops receiving fixes without anything appearing to change.

Check what you are actually running

The version that matters is the package version, not the upstream one. Distributions backport security fixes without changing the number before the dash, so a release that looks years old is frequently fully patched, and the revision after the dash is the only part that tells you.

dpkg-query -W -f='${Package} ${Version}\n' mariadb-server mariadb-client 2>/dev/null

rpm -q mariadb-server mariadb

Fixed versions, per distribution

Each distribution patches on its own schedule and under its own version scheme, so the same CVE has a different answer on each of them. These come from the distributions’ own advisory data, asked per release. Where a release has no fixed version, that is what the advisory says, not a gap in the data.

Advisory data last refreshed 26 September 2026. It is re-read daily.

What this page does not tell you

It does not tell you whether your server is affected. A CVE applying to a package is not the same as a CVE applying to your installation: the fix may already be backported into what you are running, the vulnerable module may not be loaded, or the service may not be reachable from anywhere that matters. Answering that needs the versions on your machine, not a list.

It also carries no count of how many servers are affected. SecAI monitors a small fleet, and a percentage drawn from it would be arithmetic on a sample too small to mean anything. When that changes, the number will appear here and the page will say when it started.

Read next