MySQL 4.0 · Version Status
MySQL 4.0 End of Life Date
MySQL 4.0 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
⚠
MySQL 4.0 is past end of life. This version no longer receives security patches. 6612 days past EOL — migrate to a supported version immediately.
EOL Date
Sep 30, 2008
6612 days past EOL
Latest Release
4.0.30
Standard release
Release Date
Mar 15, 2003
MySQL 4.0 series
Where these dates come from
End of lifeSep 30, 2008endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees End of active supportSep 30, 2006endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees ReleaseMar 15, 2003endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale.
How we source dates.
Lifecycle detail
MySQL 4.0 was released on March 15, 2003 and support ended on September 30, 2008 — a supported lifespan of 5 years and 7 months, in line with the 5 years and 1 month median for MySQL releases. It was not an LTS release; MySQL reserves longer patch windows for its LTS releases. Its latest release on record is 4.0.30, published February 16, 2007 — 1 year and 8 months before support ended. It has been past its end-of-life date for 18 years and 1 month. 19 newer MySQL releases have shipped since.
Attack Surface
30/30 Critical tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build.
Methodology → ·
View score card →
Extended Support
Extended MySQL 4.0 support options
Some vendors and third parties sell security patches beyond end of life; whether one covers this version varies. Compare your options.
Compare Options →
| Version | Latest | EOL Date | Status |
|---|
| 3.23 |
3.23.58 |
Dec 31, 2006 |
EOL |
| → 4.0 |
4.0.30 |
Sep 30, 2008 |
EOL |
| 4.1 |
4.1.24 |
Dec 31, 2009 |
EOL |
| 5.0 |
5.0.96 |
Dec 31, 2011 |
EOL |
| 5.1 |
5.1.73 |
Dec 31, 2013 |
EOL |
| 5.5 |
5.5.63 |
Dec 31, 2018 |
EOL |
| 5.6 |
5.6.51 |
Feb 28, 2021 |
EOL |
| 5.7 |
5.7.44 |
Oct 31, 2023 |
EOL |
What does MySQL 4.0 end of life mean?
When MySQL 4.0 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running MySQL 4.0 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to MySQL 26.10 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does MySQL 4.0 reach end of life?
MySQL 4.0 reached end of life on September 30, 2008. This version is no longer receiving security patches.
Is MySQL 4.0 still supported?
No. MySQL 4.0 reached end of life on September 30, 2008 and is no longer receiving security patches.
What should I upgrade to from MySQL 4.0?
The recommended upgrade from MySQL 4.0 is
MySQL 26.10 — the latest actively supported version. Check the
MySQL full timeline for all supported versions.
What are the security risks of running MySQL 4.0 past EOL?
Since MySQL 4.0 reached end of life, the maintainers no longer issue security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL MySQL should migrate immediately or implement compensating controls.
Does MySQL track end-of-life by point release (e.g. MySQL 26.10.1, MySQL 26.10.2)?
No — MySQL end-of-life dates apply to the entire 26.10.x release series, not individual point releases. A point release like MySQL 26.10.1 or MySQL 26.10.2 shares the same EOL date as MySQL 26.10. Security patches stop for the entire 26.10.x line on that date, regardless of which patch version you are running. Check the table above for EOL dates by major version series.