MySQL on Linux: which version fixes what

What it is, and why it is on your server

MySQL is Oracle's relational database, shipped by Ubuntu as mysql-8.0. Debian does not package it at all and ships MariaDB in its place, which is why the Debian columns on this page say so rather than showing zero.

Why its advisories behave the way they do

• Oracle ships CVEs in quarterly batches. A single critical patch update can name dozens at once, so a jump of forty in the count is a release schedule, not an event.
• Most require authentication, which means the real question is who can reach port 3306. A database bound to 0.0.0.0 turns an authenticated flaw into an internet-facing one.
• The client library has its own advisories. Applications link libmysqlclient, and patching the server does not patch them.

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' mysql-server mysql-client 2>/dev/null

rpm -q mysql-server mysql

Check what it is listening on with `ss -lntp | grep 3306`. Bound to 127.0.0.1 is a very different server from bound to 0.0.0.0.

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 28 October 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