MariaDB End-of-Life Dates —
Official EOL Schedule for Every Version
MariaDB 10.6 LTS reached end of life on July 6, 2026 — it no longer receives security fixes of any kind. Every 10.x release except 10.11 LTS is now past EOL; a 10.6 server today accumulates unpatched CVEs with each new disclosure, and databases collect exactly the vulnerabilities attackers industrialize first. The supported LTS destinations are 10.11 (to February 2028), 11.4 (to May 2029), 11.8 (to June 2028), and 12.3 — and the 10.x→11.x shift catches teams off guard: the LTS cadence changed, and the upgrade path is not always obvious.
If migration can't land soon, third-party vendors sell continued security patching for EOL MariaDB versions as a bridge — the options, compared.
This page is the single reference for MariaDB end-of-life dates across every version — with EOL Risk Scores™, LTS vs rolling release explained, and a plain-English upgrade guide.
Key Dates at a Glance
- MariaDB 10.5 LTS: end of life 2025-06-24
- MariaDB 10.6 LTS: end of life 2026-07-06
- MariaDB 10.11 LTS: end of life 2028-02-16
- MariaDB 11.8 LTS: end of life 2028-06-04
- MariaDB 11.4 LTS: end of life 2029-05-29
- MariaDB 12.3 LTS: released 2026-05-28; end of life 2029-06-12
- MariaDB 12.2 (rolling): end of life 2026-05-28
- Complete MariaDB EOL schedule — all versions
- LTS vs rolling releases — what it means for EOL
- MariaDB 10.6 LTS — EOL July 6, 2026
- MariaDB 10.11 LTS — supported until February 2028
- MariaDB 11.4 LTS — supported until May 2029
- MariaDB 11.8 LTS — recommended upgrade target
- MariaDB 12.3 LTS — newest LTS, EOL June 12, 2029
- MariaDB vs MySQL — EOL implications
- How to upgrade safely
- Frequently asked questions
Complete MariaDB EOL Schedule
MariaDB maintains two types of releases: LTS (Long-Term Support) releases with multi-year support windows, and rolling releases with short support windows of one to two years. Most production databases should be on an LTS release. Rolling releases are for teams that want access to new features faster and are prepared to upgrade frequently.
| Version | Type | Released | End of Life | Status | EOL Risk Score™ |
|---|---|---|---|---|---|
| MariaDB 10.4 | LTS | Jun 2019 | Jun 18, 2024 | EOL | 70 |
| MariaDB 10.5 | LTS | Jun 2020 | Jun 24, 2025 | EOL | 65 |
| MariaDB 10.6 | LTS | Jul 2021 | Jul 6, 2026 | EOL | 55 |
| MariaDB 10.11 | LTS | Feb 2023 | Feb 16, 2028 | Supported | 30 |
| MariaDB 11.4 | LTS | May 2024 | May 29, 2029 | Supported | 30 |
| MariaDB 11.8 | LTS | Jun 4, 2025 | Jun 4, 2028 | Supported | 30 |
| MariaDB 12.3 | LTS | May 28, 2026 | Jun 12, 2029 | Newest LTS | 30 |
LTS vs Rolling Releases — What It Means for EOL
MariaDB's versioning changed significantly with the 11.x series, and understanding it is essential for EOL planning.
LTS releases (10.4, 10.5, 10.6, 10.11, 11.4, 11.8, and 12.3) receive 5 years of support. These are the versions you should be running in production. Since 11.x, MariaDB designates one LTS per year — the second-quarter release: 11.4 (May 2024), 11.8 (June 2025), 12.3 (May 2026) — each supported for five years.
Rolling releases (10.7, 10.8, 10.9, 10.10, 11.0, 11.1, 11.2, 11.3, 11.5, 11.6, 11.7, 12.0, 12.1, 12.2) are supported only until the next quarterly release ships — roughly three months (12.2, released February 13, 2026, ended May 28, 2026 the day 12.3 shipped). They are feature preview releases meant for teams that want to test upcoming functionality. Running a rolling release in a production database is a common mistake — it looks like a newer version but has a shorter support window than the LTS it preceded.
MariaDB 10.6 LTS — EOL July 6, 2026
MariaDB 10.6 was released in July 2021 as the successor to 10.5, bringing window functions improvements, infinite precision decimals, atomic DDL, and performance improvements across the board. It became the go-to LTS version for many organizations upgrading from 10.4 and 10.5.
Its 5-year LTS window closed July 6, 2026. Since that date, MariaDB Corporation has stopped issuing security patches for community 10.6. Commercial extended support is available through MariaDB Enterprise for organizations that need more time — but at cost, and with a defined migration requirement.
Now that the July 6, 2026 EOL date has passed, 10.6's EOL Risk Score™ climbs steadily as the days-past-EOL factor increases — check the live score for the current value.
Target version: Upgrade to MariaDB 10.11 LTS (supported until February 2028) or MariaDB 11.4 LTS (supported until May 2029). Both are well-tested upgrade targets from 10.6.
MariaDB 10.11 LTS — Supported Until February 2028
MariaDB 10.11 is the last LTS in the 10.x series — the final chapter before the architectural changes introduced in 11.x. If you're upgrading from 10.6 and want a conservative step before moving to 11.x, 10.11 is the right target. It's actively supported until February 2028, giving you nearly two years of runway.
10.11 introduced improvements to replication, performance schema, and InnoDB. The upgrade path from 10.6 to 10.11 is well-documented and generally smooth for applications that haven't relied on deprecated features.
Good for: Teams upgrading from 10.6 who want to stay in the familiar 10.x feature set before planning a larger 11.x migration.
MariaDB 11.4 LTS — Supported Until May 2029
MariaDB 11.4 is the first LTS release in the 11.x series and represents the modern MariaDB architecture. It brings UUID data type, natural sort order, enhanced JSON support, and significant optimizer improvements. Support runs through May 2029 — the longest runway of any currently available LTS version.
If you're planning a major upgrade from 10.6 and have the capacity to test thoroughly, 11.4 is the best long-term choice. You won't need to upgrade again for three years.
Good for: Teams doing a planned migration who want maximum support runway and access to modern MariaDB features.
MariaDB 11.8 LTS — Recommended Upgrade Target, EOL June 4, 2028
MariaDB 11.8 reached GA on June 4, 2025 and is supported until June 4, 2028. It is the recommended target for most upgrades today: mature, with a year of production hardening; MariaDB 12.3 LTS (May 28, 2026, supported to June 12, 2029) is the newest LTS and the right choice for greenfield deployments that want the longest runway.
For teams upgrading from 10.6, a direct jump to 11.8 is possible but requires the most testing. The 11.x series introduced changes to replication, binlog format, and some SQL mode defaults that may require application-level changes.
MariaDB 12.3 LTS — Newest LTS, EOL June 12, 2029
MariaDB 12.3 reached GA on May 28, 2026 and is supported until June 12, 2029 — the fourth LTS under the one-per-year model after 10.11, 11.4 and 11.8. It closed the 12.x rolling series (12.0, 12.1 and 12.2 are all end of life; 12.2 died the day 12.3 shipped). Choose it for new deployments and for teams that want the longest runway; teams upgrading from 10.6 or 10.11 usually land on 11.8 first, then move to 12.3 on their own schedule.
MariaDB vs MySQL — EOL Implications
MariaDB started as a MySQL fork in 2009 when Oracle acquired MySQL. The two databases have diverged significantly since then — particularly in the 10.x and 11.x series — but many teams still run MariaDB on infrastructure originally provisioned for MySQL, and the MySQL vs MariaDB EOL question comes up frequently in upgrade planning.
They are not interchangeable at EOL. A MySQL 8.0 EOL date does not apply to MariaDB 10.6, and vice versa. The databases have different release schedules, different LTS policies, and different vendor support structures. If your infrastructure documentation says "MySQL compatible" but you're running MariaDB, you need to track MariaDB EOL dates specifically.
Migrating from MariaDB to MySQL (or vice versa) at EOL is high risk. If your team is considering a database swap as part of an EOL migration, treat it as a full database migration project — not a version upgrade. Schema compatibility issues, replication format differences, and application query behavior can all differ in ways that don't surface until production load hits.
Amazon RDS for MariaDB has its own EOL schedule. If you're running MariaDB on Amazon RDS, check the RDS for MariaDB support dates separately — they trail community EOL dates by months in some cases. Check the EOL Checker for RDS-specific dates.
MariaDB currently carries an EOL Risk Score™ of 55/100 — Grade C, elevated risk, recalculated at every site build from EOL recency, attack surface, CISA KEV exposure, and extended-support availability. Per-version scores and dates are on the MariaDB lifecycle page.
The right response comes down to 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 fees paid repeatedly cost more than doing the project once. Indefinitely, migrate now and plan the next one before it surprises you. Extended support is often the more expensive choice over a multi-year horizon — a bridge, not a destination. And if this deadline feels like vendor caprice, it isn’t — why end of life is inevitable for every version, with the receipts.
How to Upgrade Safely
-
01Confirm your current version and release type Run
SELECT VERSION();on your database. Cross-reference the version number against the table above — confirm whether you're on an LTS or rolling release. If you're on a rolling release that's already past EOL, you may not have noticed because the version number looks "newer" than an LTS still in support. -
02Choose your target version For most teams on 10.6: upgrade to 10.11 for a conservative step, or 11.4 for the best long-term position. For teams on 10.4 or 10.5: go directly to 11.4 or 11.8 — you're already multiple versions behind and a two-step upgrade through 10.11 adds unnecessary complexity.
-
03Run mysql_upgrade and check for incompatibilities MariaDB provides
mariadb-upgrade(formerlymysql_upgrade) to update system tables and check for incompatibilities. Run this in your staging environment first. Pay attention to any deprecated functions, removed storage engines, or changed SQL mode defaults that your application may be relying on. -
04Test replication carefully If you're running replication, upgrade replicas before the primary. Mixed-version replication (primary on newer version, replicas on older) is supported during the upgrade window but should be temporary. Validate that binary log format and GTID settings are consistent across the topology after upgrade.
-
05Back up before every step Take a full backup with
mariabackupormysqldumpbefore upgrading. Test that the backup restores successfully. This sounds obvious but is skipped more often than it should be — especially under audit-driven upgrade pressure. -
06Consider commercial extended support if you need time MariaDB Corporation offers Enterprise support with extended lifecycle for LTS versions — 2 additional years standard, up to 5 years with extended options. Since 10.6 is now past EOL, any still-running migration means evaluating whether enterprise support is worth the cost versus accelerating the upgrade timeline.
Frequently Asked Questions
Is MariaDB 10.6 still supported?
No. MariaDB 10.6 LTS reached end of life on July 6, 2026 and receives no further security fixes from MariaDB. Upgrade to 10.11 LTS (to February 16, 2028), 11.4 (to May 29, 2029), 11.8 (to June 4, 2028) or 12.3 (to June 12, 2029); third-party vendors sell continued patching for 10.6 as a bridge.
Which MariaDB versions are LTS?
10.4, 10.5, 10.6, 10.11, 11.4, 11.8 and 12.3. Since 11.x MariaDB designates one LTS a year — the second-quarter release — each supported for five years. Everything else in 10.7–10.10, 11.0–11.3, 11.5–11.7 and 12.0–12.2 is a rolling release supported only until the next quarterly release ships.
How long are MariaDB rolling releases supported?
Roughly three months — until the next quarterly release. MariaDB 12.2 (February 13, 2026) ended May 28, 2026 the day 12.3 shipped; 12.1 lasted November 18, 2025 to February 13, 2026. Rolling releases are feature previews, not production versions.
What is the newest MariaDB LTS?
MariaDB 12.3, released May 28, 2026 and supported until June 12, 2029. MariaDB 11.8 (June 4, 2025 to June 4, 2028) is the recommended upgrade target for most estates coming off 10.6 or 10.11; 12.3 is the choice for new deployments wanting the longest runway.
When does MariaDB 10.11 reach end of life?
February 16, 2028. It is the last supported 10.x release and the smallest jump from 10.6; teams that cannot take the 11.x replication and SQL-mode changes yet can land on 10.11 and plan the 11.8/12.3 move before 2028.
How do I check my MariaDB version?
Run SELECT VERSION(); in any client, or mariadb --version and mariadbd --version from the shell. The first two numbers (10.6, 10.11, 11.8, 12.3) are the release series that decides the end-of-life date; on managed services the engine version is on the instance page.
Check your full database stack for EOL exposure
MariaDB is one component. Check your OS, runtime, and application dependencies too — free, no signup required.
Scan your stack Check a version Risk Score methodology