CISA list

MySQL versions

MySQL: no supported branch has a safe release yet. 26.7, 9.6, 9.5, 9.4, 9.3, 9.2, 9.1, 9.0 and 8.3 and older have reached end of life in the lifecycle data.

Data: .

Which MySQL branch to run

The newest safe release is the newest release of a branch that still gets fixes and that no CVE record we read names as affected. Records whose versions we cannot place on a branch are counted at the end of the page.

Which MySQL branch to run
BranchStatusNewest safe releaseUpgrade to
26.106 CVE records that this page readsBug and security fixes, no end date announcedNone yetNo safe release to move to yet
26.777 CVE records that this page readsEnded on 20 October 2026None, the branch has endedNo safe release to move to yet
9.7119 CVE records that this page readsBug and security fixes until 30 April 2031, then Extended Support until 30 April 2034None yetNo safe release to move to yet
9.6Ended on 21 April 2026None, the branch has endedNo safe release to move to yet
9.5Ended on 20 January 2026None, the branch has endedNo safe release to move to yet
9.4Ended on 21 October 2025None, the branch has endedNo safe release to move to yet
9.31 CVE record that this page readsEnded on 22 July 2025None, the branch has endedNo safe release to move to yet
9.2Ended on 15 April 2025None, the branch has endedNo safe release to move to yet
9.123 CVE records that this page readsEnded on 21 January 2025None, the branch has endedNo safe release to move to yet
9.031 CVE records that this page readsEnded on 15 October 2024None, the branch has endedNo safe release to move to yet
8.4169 CVE records that this page readsBug and security fixes until 30 April 2029, then Extended Support until 30 April 2032None yetNo safe release to move to yet
8.319 CVE records that this page readsEnded on 30 April 2024None, the branch has endedNo safe release to move to yet
8.225 CVE records that this page readsEnded on 16 January 2024None, the branch has endedNo safe release to move to yet
8.112 CVE records that this page readsEnded on 25 October 2023None, the branch has endedNo safe release to move to yet
8.0759 CVE records that this page readsEnded on 30 April 2026None, the branch has endedNo safe release to move to yet
5.7311 CVE records that this page readsEnded on 31 October 2023None, the branch has endedNo safe release to move to yet
5.6138 CVE records that this page readsEnded on 28 February 2021None, the branch has endedNo safe release to move to yet
5.552 CVE records that this page readsEnded on 31 December 2018None, the branch has endedNo safe release to move to yet
5.1Ended on 31 December 2013None, the branch has endedNo safe release to move to yet
5.0Ended on 31 December 2011None, the branch has endedNo safe release to move to yet
4.1Ended on 31 December 2009None, the branch has endedNo safe release to move to yet
4.0Ended on 30 September 2008None, the branch has endedNo safe release to move to yet
3.23Ended on 31 December 2006None, the branch has endedNo safe release to move to yet

What this page counts

The branches, their dates and the newest release of each are from the product lifecycle data credited under Sources. A later release that a CVE record names as a fix counts as the newest too.

1,041 CVE records that Oracle's CVE Numbering Authority published name MySQL in a form this page reads exactly. Each gives the releases it affects and none names the release that fixes it, so no release is shown as a fix. A record from any other source gives no version here.

No release of a branch that has ended is called safe here. Some of these branches are still named by records published after they ended; the page of each says how many.

Some records give a range with no start: from 0, or before a release. A record is placed on the branch of the release that ends its range. As the record states it, the range also covers every older release. Such a range is not counted when the newest safe release of a branch that still gets fixes is worked out.

99 records are not placed on a branch, so no branch or release row counts them: CVE-2017-10384, CVE-2019-2991, CVE-2022-21555, CVE-2025-21574, CVE-2025-21575, CVE-2025-21577, CVE-2025-21579, CVE-2025-21580, CVE-2025-21581 and CVE-2025-21584 and 89 others.

Sources
  • CVE records: Copyright © 1999-2026, The MITRE Corporation. CVE is a trademark and the CVE logo is a registered trademark of The MITRE Corporation (source). Licence: CVE Program Terms of Use
  • Product lifecycle dates from endoflife.date, Copyright 2020 endoflife.date contributors (MIT License) (source). Licence: MIT License
  • EPSS scores by FIRST (https://www.first.org/epss/), generated by Empirical Security (source)