MySQL 5.0 End of Life
Support dates, vulnerabilities published since end of life, and upgrade guidance — rebuilt from live data.
MySQL 5.0 reached end of life on December 2011. It no longer receives security fixes.
Support timeline
Official dates, read directly from oracle.com, dev.mysql.com and docs.oracle.com.
| Milestone | Date | Status |
|---|---|---|
| Initial release | October 2005 | 21y ago |
| Extended Support ended | December 2011 | 14y 10mo ago |
| Latest release | — | final |
The cost of staying: CVEs since end of life
1234 MySQL vulnerabilities have been published since December 2011. All were fixed in supported branches — 5.0 received none of them. Source: NVD.
MySQL CVEs published since 5.0's EOL, by year
7 of the 1234 are rated critical · data refreshed 2026-10-05
Published 3 Mar 2016 · rated critical — fixed in supported branches only, never in 5.0. Details
Published 21 Apr 2016 · rated critical — fixed in supported branches only, never in 5.0. Details
Published 20 Sept 2016 · rated critical — fixed in supported branches only, never in 5.0. Details
Where to go from 5.0
Recommended target: MySQL 9.7 (supported until April 2034).
The newest actively supported branch is MySQL 9.7 (latest release 9.7.3). Review dev.mysql.com before upgrading.
Frequently asked questions
Is MySQL 5.0 still safe to use?
No. MySQL 5.0 stopped receiving security fixes on December 2011. Since then, 1234 MySQL vulnerabilities have been published and fixed in supported branches — MySQL 5.0 received none of those fixes.
Can I still download MySQL 5.0?
Yes — the final release (5.0) generally remains available from vendor archives and OS package mirrors, but installing it means running software with known, unpatched vulnerabilities.
What should I upgrade MySQL 5.0 to?
Upgrade to MySQL 9.7, the newest actively supported branch (supported until April 2034).