circle-info
Webinar | Deploy MariaDB Cloud in Your Microsoft Azure Account. Retain Control.
Watch Nowarrow-up-right
search
Download MariaDBContact Us

Changelog 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

hashtag
Issues Fixed

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

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

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

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

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

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

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

  • 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-2466arrow-up-right)

  • On IA-32 and AMD64 depending on the build options, the server could crash due to an unaligned access when sending data to a client connection. (MDEV-37148arrow-up-right)

  • ed25519 client authentication plugin would fail to load for anything but mariadb client utility. This has been fixed now. (MDEV-37527arrow-up-right)

  • 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-37558arrow-up-right)

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

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

  • Memory leak in innodb.import_hidden_fts_debug (MDEV-38391arrow-up-right)

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

  • 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. Concerns only Enterprise Server as only it enables Galera encryption, all versions: 10.5, 10.6, 11.4, 11.8 (MENT-2474arrow-up-right)

  • The fix is in galera library and was pushed as part of the duplicate issue MENT-2512 (MENT-2489arrow-up-right)

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

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

  • 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-28823arrow-up-right)

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

  • function VALUE() cloned incorrectly before the fix (MDEV-36888arrow-up-right)

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

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

  • 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-37755arrow-up-right)

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

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

  • 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-38041arrow-up-right)

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

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

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

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

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

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

spinner

Last updated

Was this helpful?