MariaDB 10.6 end of life
MariaDB 10.6 reached community end of life on 6 July 2026, five years after its GA release on 6 July 2021, according to the MariaDB Foundation's maintenance policy. The Foundation lists enterprise maintenance through mariadb.com to 23 August 2028 and an extended option to 23 August 2029. The community LTS lines to move to are 10.11, 11.4, 11.8 and 12.3.
- End of life
- 6 July 2026
- Released
- Jul 2021
- Final release
- 10.6.28 (latest listed, 13 August 2026)
- Successor
- MariaDB 11.4 or 12.3 LTS (10.11 and 11.8 also supported)
Date published by MariaDB Foundation maintenance policy. We do not publish a lifecycle date we cannot source.
Last reviewed
What actually stops on 6 July 2026
- Community maintenance under the Foundation's published policy. mariadb.org still lists 10.6.28, released on 13 August 2026, but any community release after 6 July 2026 falls outside that commitment.
- Planned fixes for bugs and vulnerabilities reported against 10.6. Fixes that land in 10.11 and later have no committed community 10.6 release.
- Free vendor maintenance. What remains for 10.6 is commercial: mariadb.com's enterprise maintenance to 23 August 2028 and its extended option to 23 August 2029.
What actually breaks in the upgrade
Choose the target by its end date
Community maintenance runs to 16 February 2028 for 10.11, 29 May 2029 for 11.4, 4 June 2028 for 11.8 and 12 June 2029 for 12.3. 11.8 ends before 11.4 because, from 11.8, the Foundation publishes community binaries for three years instead of five. For one move that lasts, aim at 11.4 or 12.3.
You can skip releases
The Foundation states that mariadb-upgrade can upgrade database files from any older release, so a 10.6 server can go straight to 11.4 or 12.3 without stopping at 10.11. Defaults and behaviour still change across those releases, so test the application against the target release as well as the upgrade itself.
Galera clusters move one node at a time
Upgrade a single node, start it, run mariadb-upgrade and wait for wsrep_local_state_comment to report Synced before touching the next node. A cluster that runs mixed versions during the change window needs that window planned and rehearsed.
Your options, costed honestly
Including the ones that do not involve buying anything from us.
| Option | What it is | Effort | Cost | Our view |
|---|---|---|---|---|
| Upgrade to 11.4 or 12.3 LTS | One supported jump with mariadb-upgrade, community maintenance to 2029. | Weeks, mostly application testing | Engineering time | The right destination for most estates. |
| MariaDB enterprise subscription | Enterprise maintenance for 10.6 to August 2028, extended to August 2029, from mariadb.com. | Procurement | Commercial subscription | Fits teams that want builds from the company that develops MariaDB's enterprise server. |
| OSSeva patched 10.6 builds | Signed 10.6 Community Server builds with security fixes backported, in the same series. | Days | Subscription, priced per cluster | Keeps self-managed 10.6 servers patched while the upgrade is planned and rehearsed. |
| Stay on 10.6.28 unpatched | No committed community fixes after July 2026. | None | Zero now | Each quarterly MariaDB release widens the gap, and scanners will report it. |
What OSSeva does for MariaDB 10.6
OSSeva patches this line
OSSeva ships patched, signed MariaDB 10.6 Community Server builds as DEB and RPM packages, tarballs and container images on the Patch, Assure and Operate tiers. The builds stay in the 10.6 series, on the same data directory and configuration. Assure adds an upgrade plan to a current LTS, rehearsed with mariadb-upgrade, and a Galera and replication review; Operate runs the upgrade node by node.
MariaDB extended supportWhat your auditor will say
The data store is a system component in its own right. An unsupported version with no patch source is a finding; a documented third-party patch stream is the usual remediation.
Auditors ask for evidence that production systems receive security fixes. A version past end of life fails that test unless another supplier ships the fixes and can show which CVEs they close.
For EU financial entities, the ICT risk and third-party provisions apply when a critical service depends on software with no support arrangement in place.
MariaDB 10.6: common questions
What is the MariaDB 10.6 end of life date?
6 July 2026 for the community release, five years after GA. The Foundation's table lists enterprise maintenance to 23 August 2028 and the extended option to 23 August 2029, both through mariadb.com.
Is MariaDB 10.6 still supported?
Not by the community. Community maintenance ended on 6 July 2026. Commercial maintenance is available from mariadb.com, and OSSeva ships patched 10.6 builds for self-managed servers.
What should I upgrade MariaDB 10.6 to?
11.4 or 12.3, supported by the community to 29 May 2029 and 12 June 2029. 10.11 ends on 16 February 2028 and 11.8 on 4 June 2028, so both buy less time.
Can MariaDB 10.6 upgrade directly to 11.4 or 12.3?
Yes. The Foundation states that mariadb-upgrade can upgrade database files from any older release, so no stop at 10.11 is needed.
Can I get security patches for MariaDB 10.6 after end of life?
Yes. OSSeva ships patched, signed MariaDB 10.6 builds on the Patch, Assure and Operate tiers, priced per cluster.
Still running MariaDB 10.6?
Tell us the versions and the estate size. We will tell you honestly whether to upgrade or to buy cover — and we say 'upgrade' more often than you would expect.