Security support for end-of-life MySQL
MySQL 8.0 reached end of life on 30 April 2026 and MySQL 5.7 on 31 October 2023. Oracle no longer fixes them, and its advisories stop listing them. These are the versions still in use, with every vulnerability the US National Vulnerability Database lists for them.
Request a server assessmentMySQL versions past end of life
| MySQL | Ships with | End of life | Known CVEs | Critical | Exploited | Forkward |
|---|---|---|---|---|---|---|
| 5.5.63 | Last MySQL 5.5 release | 31 December 2018 | 210 | 2 | 0 | Patch on order, 48 h |
| 5.6.51 | Last MySQL 5.6 release | 28 February 2021 | 130 | 2 | 0 | Patch on order, 48 h |
| 5.7.33 | Ubuntu 16.04 | 31 October 2023 | 106 | 3 | 0 | Patch on order, 48 h |
| 5.7.42 | Ubuntu 18.04 | 31 October 2023 | 41 | 1 | 0 | Patch on order, 48 h |
| 5.7.44 | Last MySQL 5.7 release | 31 October 2023 | 36 | 1 | 0 | Patch on order, 48 h |
| 8.0.42 | Ubuntu 20.04 | 30 April 2026 | 65 | 0 | 0 | Patch on order, 48 h |
| 8.0.46 | Last MySQL 8.0 release | 30 April 2026 | 1 | 0 | 0 | Patch on order, 48 h |
Vulnerabilities from the US National Vulnerability Database, 28 October 2026, for the upstream version, counting only entries where MySQL itself is the vulnerable product. Exploited: listed in the CISA catalogue of known exploited vulnerabilities. Package versions from each distribution's public repositories. Distribution builds include some vendor fixes; your assessment shows which risks are real.
Managed databases
On Amazon RDS or Azure, the provider controls the engine and charges for extended support. We patch the databases you run on your own servers and virtual machines. All databases
Patch on order, 48 h
We backport the fix to the version you run within 48 hours of your order, or within 24 hours with priority delivery. See the plans