MariaDB 10.5 · Version Status

MariaDB 10.5 End of Life Date

MariaDB 10.5 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.

MariaDB 10.5 is past end of life. This version no longer receives security patches. 389 days past EOL — migrate to a supported version immediately.
EOL Date
Jun 24, 2025
389 days past EOL
Latest Release
10.5.29
LTS release
Release Date
Jun 24, 2020
MariaDB 10.5 series
← MariaDB 10.4 All MariaDB versions MariaDB 10.6 →
65 / 100
High Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
35/40
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 →
Recommended upgrade path
MariaDB 12.3
Latest release: 12.3.2 · EOL: Jun 30, 2029
View full MariaDB timeline →
Extended Support
Extended MariaDB 10.5 support is available

Commercial vendors offer security patches beyond EOL — compare your options.

Compare Options →
All MariaDB Versions
VersionLatestEOL DateStatus
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 10.5 end of life mean?

When MariaDB 10.5 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 10.5 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.

Migrate to MariaDB 12.3 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does MariaDB 10.5 reach end of life?
MariaDB 10.5 reached end of life on June 24, 2025. This version is no longer receiving security patches.
Is MariaDB 10.5 still supported?
No. MariaDB 10.5 reached end of life on June 24, 2025 and is no longer receiving security patches.
What should I upgrade to from MariaDB 10.5?
The recommended upgrade from MariaDB 10.5 is MariaDB 12.3 — the latest actively supported version. Check the MariaDB full timeline for all supported versions.
What are the security risks of running MariaDB 10.5 past EOL?
When MariaDB 10.5 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.
Does MariaDB track end-of-life by point release (e.g. MariaDB 12.3.1, MariaDB 12.3.2)?
No — MariaDB end-of-life dates apply to the entire 12.3.x release series, not individual point releases. A point release like MariaDB 12.3.1 or MariaDB 12.3.2 shares the same EOL date as MariaDB 12.3. Security patches stop for the entire 12.3.x line on that date, regardless of which patch version you are running. Check the table above for EOL dates by major version series.
Deep Dive
Full Guide
MariaDB End of Life: Complete Version Support and EOL Dates
Data from endoflife.date API · Generated at build time · How we source data →
Related Products
MySQLPostgreSQLPHPPython