Mariadb End of Life Dates

database

Mariadb is a widely-used database management system that has been a staple in the development community since its inception. Created as a fork of MySQL, Mariadb has been maintained by the MariaDB Corporation Ab and the community at large, with the goal of providing a reliable and feature-rich database solution. Developers use Mariadb due to its robustness, scalability, and compatibility with a wide range of applications, making it an essential tool for building and deploying database-driven systems. With a history spanning multiple years, Mariadb has undergone significant development, resulting in 29 total versions, with the latest stable version being 12.3.2.

The end-of-life landscape for Mariadb is complex, with 24 versions having already reached the end of their support lifecycle. Currently, only 5 versions remain actively supported, giving developers a limited window to plan and execute upgrades. A key date to watch out for is July 6, 2026, when version 10.6 is set to expire, marking the next significant milestone in the Mariadb end-of-life timeline. This follows closely on the heels of the last end-of-life date, which occurred on May 13, 2026, for version 12.2. As the Mariadb ecosystem continues to evolve, staying on top of these deadlines is crucial for ensuring the security and stability of database-driven applications.

From a security perspective, Mariadb has a total of 56 tracked CVEs, with none of them being classified as critical. The most affected version is 11.4, which has 3 associated CVEs, highlighting the importance of monitoring and addressing potential vulnerabilities. Fortunately, the absence of critical CVEs suggests that Mariadb's security posture is relatively strong. Nevertheless, developers should remain vigilant and take proactive steps to ensure the security of their Mariadb deployments, such as regularly reviewing and applying security patches, as well as planning upgrades to supported versions to mitigate potential risks and maintain the overall health of their database systems.

Last updated: Oct 23, 2026

VersionReleasedActive supportEOL dateUntil EOLLatestCVEsStatusAlert me
13.0 Sep 15, 2026—Dec 31, 2026in 69d13.0.2—EOL soon
12.3 LTSMay 28, 2026—Jun 12, 2029in 963d12.3.3Active
12.2 Feb 13, 2026—May 28, 2026148d ago12.2.2EOL
12.1 Nov 18, 2025—Feb 13, 2026252d ago12.1.2EOL
12.0 Aug 7, 2025—Nov 18, 2025339d ago12.0.2EOL
11.8 LTSJun 4, 2025—Jun 4, 2028in 590d11.8.9Active
11.7 Feb 12, 2025—May 12, 2025529d ago11.7.2EOL
11.6 Nov 13, 2024—Feb 13, 2025617d ago11.6.2EOL
11.5 Aug 14, 2024—Nov 21, 2024701d ago11.5.2EOL
11.4 LTSMay 29, 2024—May 29, 2029in 949d11.4.13Active
11.3 Feb 16, 2024—May 29, 2024877d ago11.3.2EOL
11.2 Nov 21, 2023—Nov 21, 2024701d ago11.2.6EOL
11.1 Aug 21, 2023—Aug 21, 2024793d ago11.1.6EOL
11.0 Jun 6, 2023—Jun 6, 2024869d ago11.0.6EOL
10.11 LTSFeb 16, 2023—Feb 16, 2028in 481d10.11.19Active
10.10 Nov 7, 2022—Nov 17, 20231071d ago10.10.7EOL
10.9 Aug 15, 2022—Aug 22, 20231158d ago10.9.8EOL
10.8 May 20, 2022—May 20, 20231252d ago10.8.8EOL
10.7 Feb 8, 2022—Feb 9, 20231352d ago10.7.8EOL
10.6 LTSJul 6, 2021—Jul 6, 2026109d ago10.6.28EOL
10.5 LTSJun 24, 2020—Jun 24, 2025486d ago10.5.29EOL
10.4 LTSJun 18, 2019—Jun 18, 2024857d ago10.4.34EOL
10.3 May 25, 2018—May 25, 20231247d ago10.3.39EOL
10.2 May 23, 2017—May 23, 20221614d ago10.2.44EOL
10.1 Oct 17, 2015—Oct 17, 20202197d ago10.1.48EOL
10.0 Mar 31, 2014—Mar 31, 20192763d ago10.0.38EOL
5.5 LTSApr 11, 2012—Apr 11, 20202386d ago5.5.68EOL
5.3 Feb 29, 2012—Mar 1, 20173523d ago5.3.12EOL
5.2 Nov 10, 2010—Nov 10, 20154000d ago5.2.14EOL
5.1 Feb 1, 2010—Feb 1, 20154282d ago5.1.67EOL

Data sourced from endoflife.date · CVE data from NVD

Related technologies

Frequently Asked Questions