Mariadb 5.2 · Version Status
Mariadb 5.2 End of Life Date
Mariadb 5.2 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
⚠
Mariadb 5.2 is past end of life. This version no longer receives security patches. 3833 days past EOL — migrate to a supported version immediately.
EOL Date
Nov 10, 2015
3833 days past EOL
Latest Release
5.2.14
Standard release
Release Date
Nov 10, 2010
Mariadb 5.2 series
| Version | Latest | EOL Date | Status |
|---|
| 5.1 |
5.1.67 |
Feb 1, 2015 |
EOL |
| → 5.2 |
5.2.14 |
Nov 10, 2015 |
EOL |
| 5.3 |
5.3.12 |
Mar 1, 2017 |
EOL |
| 5.5 LTS |
5.5.68 |
Apr 11, 2020 |
EOL |
| 10.0 |
10.0.38 |
Mar 31, 2019 |
EOL |
| 10.1 |
10.1.48 |
Oct 17, 2020 |
EOL |
| 10.2 |
10.2.44 |
May 23, 2022 |
EOL |
| 10.3 |
10.3.39 |
May 25, 2023 |
EOL |
What does Mariadb 5.2 end of life mean?
When Mariadb 5.2 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: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Mariadb 5.2 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Mariadb 11.8 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Mariadb 5.2 reach end of life?
Mariadb 5.2 reached end of life on November 10, 2015. This version is no longer receiving security patches.
Is Mariadb 5.2 still supported?
No. Mariadb 5.2 reached end of life on November 10, 2015 and is no longer receiving security patches.
What should I upgrade to from Mariadb 5.2?
The recommended upgrade from Mariadb 5.2 is
Mariadb 11.8 — the latest actively supported version. Check the
Mariadb full timeline for all supported versions.
What are the security risks of running Mariadb 5.2 past EOL?
When Mariadb 5.2 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Mariadb should migrate immediately or implement compensating controls.