MariaDB End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all MariaDB versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Extended Support | Days | Status |
|---|---|---|---|---|---|---|
| 5.1 | 5.1.67 | Feb 1, 2010 | Feb 1, 2015 | — | 4207 days past EOL | EOL |
| 5.2 | 5.2.14 | Nov 10, 2010 | Nov 10, 2015 | — | 3925 days past EOL | EOL |
| 5.3 | 5.3.12 | Feb 29, 2012 | Mar 1, 2017 | — | 3448 days past EOL | EOL |
| 5.5 LTS | 5.5.68 | Apr 11, 2012 | Apr 11, 2020 | — | 2311 days past EOL | EOL |
| 10.0 | 10.0.38 | Mar 31, 2014 | Mar 31, 2019 | — | 2688 days past EOL | EOL |
| 10.1 | 10.1.48 | Oct 17, 2015 | Oct 17, 2020 | — | 2122 days past EOL | EOL |
| 10.2 | 10.2.44 | May 23, 2017 | May 23, 2022 | — | 1539 days past EOL | EOL |
| 10.3 | 10.3.39 | May 25, 2018 | May 25, 2023 | — | 1172 days past EOL | EOL |
| 10.4 LTS | 10.4.34 | Jun 18, 2019 | Jun 18, 2024 | — | 782 days past EOL | EOL |
| 10.5 LTS | 10.5.29 | Jun 24, 2020 | Jun 24, 2025 | Jul 16, 2025 MariaDB Enterprise support (ended) |
411 days past EOL | EOL |
| 10.6 LTS | 10.6.27 | Jul 6, 2021 | Jul 6, 2026 | Aug 23, 2029 MariaDB Enterprise support |
34 days past EOL | EOL |
| 10.7 | 10.7.8 | Feb 8, 2022 | Feb 9, 2023 | — | 1277 days past EOL | EOL |
| 10.8 | 10.8.8 | May 20, 2022 | May 20, 2023 | — | 1177 days past EOL | EOL |
| 10.9 | 10.9.8 | Aug 15, 2022 | Aug 22, 2023 | — | 1083 days past EOL | EOL |
| 10.10 | 10.10.7 | Nov 7, 2022 | Nov 17, 2023 | — | 996 days past EOL | EOL |
| 10.11 LTS | 10.11.18 | Feb 16, 2023 | Feb 16, 2028 | — | 556 days remaining | Active |
| 11.0 | 11.0.6 | Jun 6, 2023 | Jun 6, 2024 | — | 794 days past EOL | EOL |
| 11.1 | 11.1.6 | Aug 21, 2023 | Aug 21, 2024 | — | 718 days past EOL | EOL |
| 11.2 | 11.2.6 | Nov 21, 2023 | Nov 21, 2024 | — | 626 days past EOL | EOL |
| 11.3 | 11.3.2 | Feb 16, 2024 | May 29, 2024 | — | 802 days past EOL | EOL |
| 11.4 LTS | 11.4.12 | May 29, 2024 | May 29, 2029 | Jan 16, 2033 MariaDB Enterprise support |
1024 days remaining | Active |
| 11.5 | 11.5.2 | Aug 14, 2024 | Nov 21, 2024 | — | 626 days past EOL | EOL |
| 11.6 | 11.6.2 | Nov 13, 2024 | Feb 13, 2025 | — | 542 days past EOL | EOL |
| 11.7 | 11.7.2 | Feb 12, 2025 | May 12, 2025 | — | 454 days past EOL | EOL |
| 11.8 LTS | 11.8.8 | Jun 4, 2025 | Jun 4, 2028 | Oct 22, 2033 MariaDB Enterprise support |
665 days remaining | Active |
| 12.0 | 12.0.2 | Aug 7, 2025 | Nov 18, 2025 | — | 264 days past EOL | EOL |
| 12.1 | 12.1.2 | Nov 18, 2025 | Feb 13, 2026 | — | 177 days past EOL | EOL |
| 12.2 | 12.2.2 | Feb 13, 2026 | May 28, 2026 | — | 73 days past EOL | EOL |
| 12.3 LTS | 12.3.2 | May 28, 2026 | TBD | — | Supported | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/mariadb)
What does MariaDB end of life mean for your organization?
When a version of MariaDB reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL MariaDB should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Your options when MariaDB reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL MariaDB versions. This is a bridge, not a permanent solution — plan your migration in parallel.
MariaDB has 25 versions past end of life — security patches have stopped, but CVE disclosures haven't. The good news: extended support for MariaDB exists — vetted vendors ship security patches for years past the official date. Tell us where to reach you and we'll reply with matched options and pricing guidance.