← Back to Blog

MariaDB Server 12.3, 11.8, 11.4 and 10.11 – Q4 2026 Maintenance Releases

Another quarter, another round of MariaDB Server maintenance releases!

On November 16, 2026, we released updates for our four currently maintained Long Term Support (LTS) series:

As usual, these releases bring bug fixes, stability improvements, and security-related corrections across MariaDB Server.

Maintenance releases might not attract as much attention as new versions introducing exciting features, but they are just as important, especially for those running MariaDB in production.

What’s included in these releases?

This quarter’s releases include a substantial number of fixes across MariaDB Server, including InnoDB, replication, Galera Cluster, the optimizer, and several storage engines.

A few areas are particularly worth mentioning.

InnoDB reliability and crash recovery

InnoDB continues to receive significant attention, with improvements addressing crash recovery, buffer pool management, and data integrity.

Among the fixes are issues involving recovery after interrupted DDL operations, handling of renamed tables during crash recovery, and potential corruption affecting certain indexed or system-versioned tables.

The newer LTS branches also benefit from improvements to buffer pool page eviction, reducing contention in the buffer pool.

These changes may not be immediately noticeable, but they are exactly the kind of improvements that matter when a database must remain reliable, even when things go wrong.

Security and privilege handling

Several fixes address privilege validation, authentication, and memory-safety issues.

These include corrections involving the CONNECT storage engine, privilege checks for specific SQL operations, and handling of certain malformed inputs.

Security is an ongoing process, and regular maintenance releases are an important part of keeping deployments protected.

Replication and Galera Cluster

Replication and clustering also benefit from this round of updates.

The fixes cover several Galera Cluster scenarios, including foreign key handling, GTID behavior, DDL operations, and State Snapshot Transfers (SST).

For users relying on replication or Galera for high availability, these corrections are another good reason to keep their servers up to date.

Query correctness and optimizer fixes

A database must not only execute queries efficiently; it must return the correct results.

This round of maintenance also addresses optimizer issues and SQL edge cases that could produce incorrect results or unexpected failures.

From JSON processing to index access and query transformations, these improvements contribute to the correctness and predictability of MariaDB Server.

Of course, these are just a few examples. The complete list of changes is available in the release notes and changelogs.

Release notes and changelogs

You can find the detailed information for each release below.

MariaDB 12.3.4

MariaDB 11.8.10

MariaDB 11.4.14

MariaDB 10.11.20

If you are running one of these LTS series, we recommend reviewing the corresponding release notes and planning your upgrade.

Four maintained LTS series, and a reminder about 10.6

As mentioned in our previous maintenance release announcement, MariaDB Community Server 10.6 reached End of Life on July 6, 2026.

Our four maintained Community LTS series are:

MariaDB ServerCommunity maintenance until
12.3June 2029
11.8June 2028
11.4May 2029
10.11February 2028

If you are still using MariaDB 10.6, don’t postpone your migration.

And if you are considering an upgrade, why not take the opportunity to discover what MariaDB Server 11.8 or 12.3 has to offer?

As always, test your applications, workloads, plugins, and configuration before upgrading production systems.

Maintenance is also innovation

When we talk about innovation in MariaDB Server, we often focus on new capabilities, SQL features, storage engines, or performance improvements.

But innovation also means improving what already exists.

Making crash recovery more reliable, fixing subtle optimizer issues, reducing contention, or correcting an obscure replication problem may not make the headlines.

Yet this work is fundamental to the quality of an Open Source database.

It is also a continuous effort. Developers investigate reported problems, contributors propose fixes, reviewers examine patches, testers verify the changes, and package maintainers make the results available to users.

Every maintenance release represents the combined effort of many people.

And that’s something worth celebrating!

But there is also a noticeable innovation coming with these new releases: the MariaDB Foundry. More to come in future articles, but this is a great improvement for everyone looking to extend MariaDB Server. With Foundry, you now have the possibility to build MariaDB Server plugins without building the server.

Thank you to our contributors!

MariaDB Server is developed in the open, and these releases are another example of the importance of collaboration.

On behalf of the MariaDB Foundation, thank you to everyone who helps make MariaDB Server better.

Whether you contribute code, report bugs, test releases, review patches, maintain packages, improve documentation, or help other users, your work matters.

A special thank you also goes to our external contributors, whose patches and improvements are an essential part of this project.

MariaDB Server is Open Source, and contributions are always welcome.

If you want to participate, take a look at our Community Contributions Process and join us.

And if your MariaDB Server is due for an update, now is a great time to plan it! 🦭

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *