Release Notes for MariaDB Enterprise Server 10.6.25-21

MariaDB Enterprise Server 10.6.25-21 is a Stable (GA) maintenance release of MariaDB Enterprise Server 10.6, released on 2026-03-17

Download Release Notes Changelog Overview of Enterprise Server 10.6

Release date: 17 Mar 2026

MariaDB Enterprise Server 10.6.25-21 is a Stable (GA) maintenance release of MariaDB Enterprise Server 10.6. This release includes a variety of fixes.

Changes in Storage Engines

• This release incorporates MariaDB ColumnStore engine version 25.10.4

Notable changes

• Galera updated to 26.4.26

Issues Fixed

Can result in data loss

• Server crash upon moving InnoDB table with fulltext index between databases (MDEV-31892)

• When innodb_buffer_pool_size is not large enough to buffer all log records during crash recovery, InnoDB may fail to recover a page from the doublewrite buffer. (MDEV-37558)

• When an inplace ALTER operation is rolled back, InnoDB drops intermediate tables and their associated FTS internal tables. However, MariaBackup's DDL tracking can incorrectly report this as a backup failure. (MDEV-38041)

Can result in hang or crash

• Fixed crash in Aria when doing a sub transaction like reading an entry from the proc table. (MDEV-23132)

• CREATE OR REPLACE ... SELECT where select used functions or sys tables could crash in debug builds, no problems with normal builds (MDEV-23298)

• innodb_undo_log_truncate=ON leads to out-of-bounds write (MDEV-37042)

• InnoDB could crash during a workload that is frequently rebuilding or dropping tables by executing statements such as TRUNCATE TABLE, OPTIMIZE TABLE, or DROP TABLE. (MDEV-37755)

• Secondary indexes could be corrupted for InnoDB tables that contain indexed virtual columns. (MDEV-38140)

• Specially crafted packet could cause the server to crash (MDEV-38242)

• The server can hang when data-at-rest encryption is used with multiple encryption threads (MDEV-38271)

• When installing mysql-selinux RPM it is no longer possible to re-start Galera nodes (MDEV-38297)

• Spider could crash when loop detection variables were artificially manipulated. (MDEV-38368)

• malformed spatial data could've caused a crash inside InnoDB (MDEV-38372)

• Long blob prefix keys could cause a crash in galera. (MDEV-38374)

• we are trying to push aggregate into WHERE (MDEV-38487)

• Fixed crash in Aria when doing a sub transaction like reading an entry from the proc table. (MENT-2424)

• A replica would crash while replicating UPDATE and DELETE DML statements that target a table which previously had a partition that was converted to a separate table via ALTER TABLE .. CONVERT PARTITION .. TO TABLE. For example, if the command looked like ALTER TABLE t1 CONVERT PARTITION p1 TO TABLE t_new; the replica would crash when trying to update/deleterows in table t1 after running the command. (MENT-2466)

• With --encrypt-binlog=ON if a node fails to apply a writeset it will crash the whole cluster due to a bug in Galera library encryption handling. Fixed in Galera library (MENT-2474)

• SET GLOBAL innodb_buffer_pool_size was prone to hang or crash the server, especially when innodb_adaptive_hash_index was enabled. (MENT-2545)

Can result in unexpected behavior

• Bogus [ERROR] InnoDB: Compressed page checksum mismatch could be reported for ROW_FORMAT=COMPRESSED tables. (MDEV-37306)

• ed25519 client authentication plugin would fail to load for anything but mariadb client utility (MDEV-37527)

• If the server was killed during an operation that creates a .ibd file, such as TRUNCATE TABLE, it could fail to recover. (MDEV-37994)

• If the server was killed during an operation that creates a .ibd file, such as TRUNCATE TABLE, it could fail to recover. (MDEV-38026)

• Auth Switch with Long Password Corrupts Database Name (MDEV-38431)

Related to Install and Upgrade

• There was a short gap when mariadb-secure-installation temporary files were potentially openable/readable by an unprivileged user. These files may contain database root password. (MDEV-28823)

Related to performance

• ASCII strings will be sent to client connections slightly faster. (MDEV-21816)

• Galera threads time out under heavy load (MENT-2289)

Unexpected results

• INSERT ... RETURNING exposes columns for which the user lacks SELECT privilege (MDEV-37950)

• Presence of Spider disables "external" XA commit (MDEV-37972)

Changelog

For the complete list of changes in this release, see the changelog.

Platforms

In alignment to the enterprise lifecycle, MariaDB Enterprise Server 10.6.24-20 is provided for:

• AlmaLinux 8 (x86_64, ARM64)

• AlmaLinux 9 (x86_64, ARM64)

• Debian 11 (x86_64, ARM64)

• Debian 12 (x86_64, ARM64)

• Oracle Linux 8 (x86_64, ARM64)

• Oracle Linux 9 (x86_64, ARM64)

• Red Hat Enterprise Linux 8 (x86_64, ARM64)

• Red Hat Enterprise Linux 9 (x86_64, ARM64, PPC64LE)

• Rocky Linux 8 (x86_64, ARM64)

• Rocky Linux 9 (x86_64, ARM64)

• SUSE Linux Enterprise Server 12 (x86_64)

• SUSE Linux Enterprise Server 15 (x86_64, ARM64)

• Ubuntu 22.04 (x86_64, ARM64)

• Ubuntu 24.04 (x86_64, ARM64)

• Microsoft Windows (x86_64) (Without MariaDB Enterprise Cluster (Galera) support)

• Red Hat UBI 8 (x86_64, ARM64)

  • Red Hat UBI 8 is part of the Enterprise Server Docker Image. It does not support MariaDB Enterprise Cluster (Galera) or MariaDB ColumnStore.

Some components of MariaDB Enterprise Server are supported on a subset of platforms. See MariaDB Engineering Policies for details.

Installation Instructions

• Deploy MariaDB Enterprise with Repositories

• Deploy MariaDB Enterprise with Package Tarballs

• Deploy MariaDB Enterprise with Docker

Upgrade Instructions

• Upgrade to MariaDB Enterprise Server 10.6

_{This page is: Copyright © 2025 MariaDB. All rights reserved.}