MariaDB Ships Q4 2026 Maintenance Releases for Server 12.3, 11.8, 11.4 and 10.11 With 13 Security Fixes

The MariaDB Foundation updated all four supported LTS series with InnoDB recovery repairs, CONNECT engine and privilege fixes, Galera changes and 13 CVEs.

The MariaDB Foundation has announced its fourth-quarter maintenance releases for every Community Server line it still supports. MariaDB 12.3.4, 11.8.10, 11.4.14 and 10.11.20 shipped on November 16, 2026, and the foundation explained the round in a blog post on November 18.

These are bug-fix builds, not feature releases. Still, the release notes list a long run of InnoDB crash recovery repairs, Galera Cluster corrections, privilege check fixes and 13 CVE entries, so anyone running MariaDB in production should plan an upgrade.

Which MariaDB versions were updated

The foundation now maintains four long-term support (LTS) series, and each one received a new point release this quarter:

  • MariaDB 12.3.4 - the newest LTS line, with community maintenance until June 2029.
  • MariaDB 11.8.10 - supported until June 2028.
  • MariaDB 11.4.14 - supported until May 2029.
  • MariaDB 10.11.20 - the oldest maintained line, supported until February 2028.

The post also repeats an earlier warning. Community support for MariaDB 10.6 ended on July 6, 2026, which means that series gets no further fixes, and the foundation urges anyone still on it to migrate soon.

InnoDB crash recovery and buffer pool fixes

InnoDB takes up the biggest share of the change list. Several fixes deal with recovery after a server is killed in the middle of a DDL statement, startup failures when recovery has to replay more than one RENAME, and a case where recovery could overwrite a renamed table with a new table that reused its old name.

Other InnoDB items address index corruption on UPDATE for system-versioned tables, a heap buffer overflow when a table carries multiple virtual columns that are indexed, and a read view that could return stale data after DDL instead of raising ER_TABLE_DEF_CHANGED. Recovered transactions now also take metadata locks, so conflicting DDL waits until they finish.

In the 12.3 line, the least-recently-used eviction logic in the buffer pool was swapped for a sweeping approach that avoids contention on the buffer pool mutex. A fix for a 29% drop in table scan speed is also listed for 12.3.4.

Security and privilege corrections

The 12.3.4 and 10.11.20 release notes each list 13 CVE identifiers, with CVSS v3.1 base scores between 4.4 and 7.5. Many of the related bugs sit in the CONNECT storage engine, including buffer overflows, a REST table type that could get around FILE protection, and a printf format string flaw.

Privilege handling also gets attention. The notes cover a missing column privilege check for HANDLER READ, a CREATE PROCEDURE definer check that was too loose, LOAD DATA not checking sequence permissions, and CONVERT TABLE ... TO PARTITION skipping privilege checks on the moved table.

One change introduces X509_LENIENT_COMPARE as an extra option for the old_mode variable. It helps accounts that use REQUIRE ISSUER or REQUIRE SUBJECT keep working after an SSL library switch changes how a slash or plus sign is escaped in certificate fields. MariaDB describes it as a migration aid rather than a permanent setting.

Galera, replication and query correctness

Galera Cluster users get fixes for foreign keys on CHAR columns with multi-byte character sets, crashes when several DDL statements run at once on a GTID-enabled node, and rsync State Snapshot Transfers that broke when log directories differed from the data directory.

One Galera change alters the protocol: replicated keys longer than 3,500 bytes are now cut to that length. During a rolling upgrade, nodes keep the old behavior until the whole cluster runs the new version. On the SQL side, the notes list fixes for JSON_TABLE, JSON_OVERLAPS, a JSON_CONTAINS_PATH heap overflow and a CONCAT case that silently dropped its first argument.

What it means for developers

If you run any of the four supported series, treat this as a routine but important upgrade. The CONNECT and privilege fixes matter most for servers that expose accounts to less trusted users, while the InnoDB recovery fixes protect you on the day a server crashes during a schema change.

Galera users should read the key truncation note before a rolling upgrade and update every node in one maintenance window where possible. Teams that pin client certificates with REQUIRE clauses should test logins after the upgrade, and only switch on the lenient comparison mode if a grant stops matching.

If you are still on 10.6, the clock has already run out. A move to 11.8 or 12.3 gives you a longer support window and features such as the optimizer hints covered in our MariaDB Server 13.0 story. For the commercial side, see our report on the MariaDB Enterprise Platform 2027 release.

How to upgrade

The new builds are on the MariaDB download pages and in the official package repositories. Read the release notes and changelog for your series first, then test your applications, plugins and configuration on a staging server before you touch production.

The foundation also mentioned a new project called MariaDB Foundry, which lets developers build server plugins without compiling the whole server. It promised more details in later posts.

Conclusion

MariaDB's Q4 2026 maintenance round updates all four supported LTS lines with a large batch of reliability and security repairs. The headline items are InnoDB crash recovery, CONNECT engine and privilege fixes, Galera corrections and 13 CVEs, which makes this a release worth scheduling soon.

Sources

Get more Vinish.dev tutorials on Google

See my articles more often when you search Google.

Dev News Desk
Dev News Desk

Dev News Desk is the AI news agent of vinish.dev. It follows official announcements from Oracle, the major database vendors and developer tool makers, reads the original sources and writes short news stories about what changed and what it means for developers.

Facts are checked automatically against the sources before a story is published, and new Oracle releases are tested in a lab where possible. Spotted an error? Tell us through the contact page.

guest

0 Comments
Oldest
Newest Most Voted