# Release Notes for MariaDB Enterprise Server 11.4.10-7

<a href="https://mariadb.com/downloads/enterprise/enterprise-server/" class="button primary">Download</a> <a href="11.4.10-7" class="button secondary">Release Notes</a> <a href="changelog-11.4.10-7" class="button secondary">Changelog</a> <a href="whats-new" class="button secondary">Overview of Enterprise Server 11.4</a>

**Release date:** 17 Mar 2026

MariaDB Enterprise Server 11.4.10-7 is a Stable (GA) maintenance release of [MariaDB Enterprise Server 11.4](https://mariadb.com/docs/release-notes/enterprise-server/11.4/whats-new). This release includes a variety of fixes.

## Changes in Storage Engines <a href="#changes-in-storage-engines" id="changes-in-storage-engines"></a>

* This release incorporates MariaDB ColumnStore engine version 25.10.4

## Notable changes <a href="#notable-changes" id="notable-changes"></a>

* [Galera](https://app.gitbook.com/o/diTpXxF5WsbHqTReoBsS/s/3VYeeVGUV4AMqrA3zwy7/) updated to 26.4.26
* Sequence Fails with Galera Version 26.4.16 and later in the Presence of enabled streaming replication ([MDEV-34124](https://jira.mariadb.org/browse/MDEV-34124))
* The HashiCorp Vault key management plugin has been updated to improve availability during intermittent network or server issues. Previously, the plugin only allowed the use of cached keys if a connection timed out. This behavior has been broadened and made the default to prevent MariaDB Server interruptions. ([MDEV-38203](https://jira.mariadb.org/browse/MDEV-38203))
  * Expanded Error Handling: The plugin now treats common connectivity issues—such as “connection refused,” “no route to host,” and “internal server error”—the same as a timeout. This ensures the server continues to function using cached keys if the Vault server is briefly unreachable.
  * Updated Defaults:
    * The option to use cached values during communication errors is now enabled by default.
    * The cache timeout is now defaulting to the maximum value.
* Audit log plugin will now log events for MariaDB Enterprise Cluster (Galera) replication applier operations with a generic user name: `<wsrep_applier>`. Before this change the user name in audit logs has been empty ([MDEV-35511](https://jira.mariadb.org/browse/MDEV-35511))

## Issues Fixed

### Can result in data loss

* Server crash upon moving InnoDB table with fulltext index between databases ([MDEV-31892](https://jira.mariadb.org/browse/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](https://jira.mariadb.org/browse/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](https://jira.mariadb.org/browse/MDEV-38041))

### Can result in hang or crash

* An issue is fixed which could result in server hangs when a replica internally scans its mysql.gtid\_slave\_pos table contents. ([MDEV-20586](https://jira.mariadb.org/browse/MDEV-20586))
* Fixed crash in Aria when doing a sub transaction like reading an entry from the proc table. ([MDEV-23132](https://jira.mariadb.org/browse/MDEV-23132))
* Wrong variable name in the configuration leads Galera to think SST/IST failed, at next restart will request a full SST ([MDEV-31517](https://jira.mariadb.org/browse/MDEV-31517))
* An unresolvable outer reference can cause a server to crash. ([MDEV-31632](https://jira.mariadb.org/browse/MDEV-31632))
* Segfault when preparing unreferenced select in recursive CTE ([MDEV-32299](https://jira.mariadb.org/browse/MDEV-32299))
* Server can crash when JSON\_SCHEMA\_VALID() is used ([MDEV-33640](https://jira.mariadb.org/browse/MDEV-33640))
* With DEFAULT() in the WHERE clause and with nested views, the server can crash ([MDEV-36686](https://jira.mariadb.org/browse/MDEV-36686))
* innodb\_undo\_log\_truncate=ON leads to out-of-bounds write ([MDEV-37042](https://jira.mariadb.org/browse/MDEV-37042))
* When using UPDATE in a BEFORE trigger, the server can crash ([MDEV-37341](https://jira.mariadb.org/browse/MDEV-37341))
* Crash with low @@optimizer\_max\_sel\_arg\_weight and optimizer\_trace=on. ([MDEV-37510](https://jira.mariadb.org/browse/MDEV-37510))
* 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](https://jira.mariadb.org/browse/MDEV-37755))
* Crash on reading corrupted view frm file ([MDEV-37920](https://jira.mariadb.org/browse/MDEV-37920))
* Galera cluster crashes when granting permission to non existing user after setting max\_error\_count and wsrep\_ignore\_apply\_errors to zero ([MDEV-37991](https://jira.mariadb.org/browse/MDEV-37991))
* crash when reading a corrupted view frm file ([MDEV-38001](https://jira.mariadb.org/browse/MDEV-38001))
* Server crashes after INSERT.. ON duplicate KEY UPDATE i = DEFAULT; ([MDEV-38096](https://jira.mariadb.org/browse/MDEV-38096))
* Sever shutdown prevented by RocksDB setting rocksdb\_pause\_background\_work ([MDEV-38110](https://jira.mariadb.org/browse/MDEV-38110))
* Secondary indexes could be corrupted for InnoDB tables that contain indexed virtual columns. ([MDEV-38140](https://jira.mariadb.org/browse/MDEV-38140))
* A large number of joins in a SELECT can crash the server ([MDEV-38168](https://jira.mariadb.org/browse/MDEV-38168))
* Specially crafted packet could cause the server to crash ([MDEV-38242](https://jira.mariadb.org/browse/MDEV-38242))
* The server can hang when data-at-rest encryption is used with multiple encryption threads ([MDEV-38271](https://jira.mariadb.org/browse/MDEV-38271))
* JSON\_SCHEMA\_VALID() crashes with a long enum ([MDEV-38356](https://jira.mariadb.org/browse/MDEV-38356))
* The authentication plugin caching\_sha2\_password can crash on large packets ([MDEV-38365](https://jira.mariadb.org/browse/MDEV-38365))
* Spider could crash when loop detection variables were artificially manipulated. ([MDEV-38368](https://jira.mariadb.org/browse/MDEV-38368))
* malformed spatial data could've caused a crash inside InnoDB ([MDEV-38372](https://jira.mariadb.org/browse/MDEV-38372))
* Long blob prefix keys could cause a crash in galera. ([MDEV-38374](https://jira.mariadb.org/browse/MDEV-38374))
* `SHOW FUNCTION CODE package_func` crashes on the second execution ([MDEV-38451](https://jira.mariadb.org/browse/MDEV-38451))
* Server crashes in setup\_returning\_fields upon 2nd execution of multi-table-styled DELETE from a view ([MDEV-38620](https://jira.mariadb.org/browse/MDEV-38620))
* 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](https://jira.mariadb.org/browse/MENT-2474))

### Can result in unexpected behaviour

* JSON\_UNQUOTE returns incorrect results depending on the collation ([MDEV-14301](https://jira.mariadb.org/browse/MDEV-14301))
* OPTIMIZE table not replicating ([MDEV-26618](https://jira.mariadb.org/browse/MDEV-26618))
* Wrong warning (Errcode: 2 "No such file or directory") shown by SHOW WARNING when a partitioned table is changed with ALTER. Only "ALGORITHM=NOCOPY is not supported for this operation. Try ALGORITHM=INPLACE" should be shown ([MDEV-35562](https://jira.mariadb.org/browse/MDEV-35562))
* A default value cannot be removed with ALTER and DROP DEFAULT default if the column is defined with NOT NULL ([MDEV-37275](https://jira.mariadb.org/browse/MDEV-37275))
* Bogus \[ERROR] InnoDB: Compressed page checksum mismatch could be reported for ROW\_FORMAT=COMPRESSED tables. ([MDEV-37306](https://jira.mariadb.org/browse/MDEV-37306))
* ed25519 client authentication plugin would fail to load for anything but mariadb client utility ([MDEV-37527](https://jira.mariadb.org/browse/MDEV-37527))
* The CHECK TABLE command can be executed by users with the table-level CREATE but not with a global CREATE privilege ([MDEV-37971](https://jira.mariadb.org/browse/MDEV-37971))
* sys.ps\_setup\_save does not restore SQL\_LOG\_BIN after error, causes replication discrepancy ([MDEV-37979](https://jira.mariadb.org/browse/MDEV-37979))
* If the server was killed during an operation that creates a .ibd file, such as TRUNCATE TABLE, it could fail to recover. ([MDEV-37994](https://jira.mariadb.org/browse/MDEV-37994))
* (Column) CHECK constraints can cause CREATE TABLE (SELECT) queries to fail ([MDEV-37998](https://jira.mariadb.org/browse/MDEV-37998))
* If the server was killed during an operation that creates a .ibd file, such as TRUNCATE TABLE, it could fail to recover. ([MDEV-38026](https://jira.mariadb.org/browse/MDEV-38026))
* event scheduler spams the error log ([MDEV-38124](https://jira.mariadb.org/browse/MDEV-38124))
* wrong result with index\_merge\_sort\_intersection and rowid\_filter=on ([MDEV-38327](https://jira.mariadb.org/browse/MDEV-38327))
* Auth Switch with Long Password Corrupts Database Name ([MDEV-38431](https://jira.mariadb.org/browse/MDEV-38431))
* Unexpected `Data too long` error on subselect as a multiplication argument ([MDEV-38626](https://jira.mariadb.org/browse/MDEV-38626))
* MariaDB sometimes reports "index is corrupted" for encrypted Aria tables, but this appears to be a false positive caused by an off-by-one check in the encryption post-read hook ([MDEV-38707](https://jira.mariadb.org/browse/MDEV-38707))

### Related to Install and Upgrade

* In case if the view mysql.user was created (e.g. in 10.6) with a server with an unexpected character\_set\_client or collation\_connection, e.g. utf8mb3 and utf8mb3\_general\_ci, mysql\_upgrade does not fix it to the expected latin1 and latin1\_swedish\_ci. ([MDEV-38698](https://jira.mariadb.org/browse/MDEV-38698))
* In case if the view mysql.user was created (e.g. in 10.6) with a server with an unexpected character\_set\_client or collation\_connection, e.g. utf8mb3 and utf8mb3\_general\_ci, mysql\_upgrade does not fix it to the expected latin1 and latin1\_swedish\_ci. ([MENT-2523](https://jira.mariadb.org/browse/MENT-2523))

### Related to performance

* ASCII strings will be sent to client connections slightly faster. ([MDEV-21816](https://jira.mariadb.org/browse/MDEV-21816))
* In multi-threaded write-heavy workloads, buf\_pool.flush\_list\_mutex could become a point of contention. ([MDEV-38069](https://jira.mariadb.org/browse/MDEV-38069))
* Poor cost calculations for index access cause bad query plans for big VARCHARs ([MDEV-38164](https://jira.mariadb.org/browse/MDEV-38164))
* Selectivity sampling for LIKE %foo% not done when the table has no sargable conditions ([MDEV-38240](https://jira.mariadb.org/browse/MDEV-38240))
* Clustered PK not used for Loose Index Scan optimization ([MDEV-38426](https://jira.mariadb.org/browse/MDEV-38426))
* Under some circumstances, some read operations could unnecessarily wait for an InnoDB log write. ([MDEV-38589](https://jira.mariadb.org/browse/MDEV-38589))
* Galera threads time out under heavy load ([MENT-2289](https://jira.mariadb.org/browse/MENT-2289))

### Unexpected results

* Unexpected success and result set upon erroneous JSON\_VALUE call ([MDEV-25148](https://jira.mariadb.org/browse/MDEV-25148))
* ST\_OVERLAPS returns true despite dim(originalInput1) ≠ dim(originalInput2) ([MDEV-35765](https://jira.mariadb.org/browse/MDEV-35765))
* On an error in CREATE TEMPORARY TABLE ... SELECT, InnoDB had internally aborted a transaction, while the server thought the transaction still existed. This caused various inconsistencies in binlog, disappeared savepoints, etc. This was fixed differently in different versions. In 10.11.16, 11.4.10, 11.8.6 the transaction is consistently and completely rolled back if CREATE TEMPORARY TABLE ... SELECT fails with an error. In 12.3.1 there is no rollback at all. ([MDEV-36787](https://jira.mariadb.org/browse/MDEV-36787))
* prohibited semijoin with rownum correctly process in HAVING rownum. ([MDEV-37157](https://jira.mariadb.org/browse/MDEV-37157))
* Incorrect results for INTERSECT ALL in ORACLE mode ([MDEV-37325](https://jira.mariadb.org/browse/MDEV-37325))
* Allow users with non-SELECT privileges to see rows in `INFORMATION_SCHEMA.TRIGGERS` table. `ACTION_CONDITION`, `ACTION_STATEMENT` and `DEFINER` columns are `NULL` unless the user is the owner of the schema or has `TRIGGER` privilege. ([MDEV-37474](https://jira.mariadb.org/browse/MDEV-37474))
* An empty value inserted for an ENUM column if a BEFORE trigger is used ([MDEV-37481](https://jira.mariadb.org/browse/MDEV-37481))
* Allow execution of multi-update/multi-delete queries within the storage engines. ([MDEV-37484](https://jira.mariadb.org/browse/MDEV-37484))
* unexpected type changing after changing AVG to MAX ([MDEV-37888](https://jira.mariadb.org/browse/MDEV-37888))
* INSERT ... RETURNING exposes columns for which the user lacks SELECT privilege ([MDEV-37950](https://jira.mariadb.org/browse/MDEV-37950))
* Presence of Spider disables "external" XA commit ([MDEV-37972](https://jira.mariadb.org/browse/MDEV-37972))
* Inconsistent behaviors when casting into time ([MDEV-38006](https://jira.mariadb.org/browse/MDEV-38006))
* Userstat Plugin CPU\_TIME much higher than BUSY\_TIME ([MDEV-38028](https://jira.mariadb.org/browse/MDEV-38028))
* Inconsistent results for make\_set of cast ([MDEV-38233](https://jira.mariadb.org/browse/MDEV-38233))
* Potentially incorrect result with having reference to group by item. ([MDEV-38473](https://jira.mariadb.org/browse/MDEV-38473))
* An issue is fixed where GRANT EXECUTE ON PROCEDURE would fail on the master, but would still be replicated and executed successfully on the slave. ([MDEV-38506](https://jira.mariadb.org/browse/MDEV-38506))

## Changelog <a href="#changelog" id="changelog"></a>

For the complete list of changes in this release, see the [changelog](https://mariadb.com/docs/release-notes/enterprise-server/11.4/changelog-11.4.10-7).

## Platforms <a href="#platforms" id="platforms"></a>

In alignment to the enterprise lifecycle, MariaDB Enterprise Server 11.4.10-7 is provided for:

* AlmaLinux 8 (x86\_64, ARM64)
* AlmaLinux 9 (x86\_64, ARM64)
* AlmaLinux 10 (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)
* Oracle Linux 10 (x86\_64, ARM64)
* Red Hat Enterprise Linux 8 (x86\_64, ARM64)
* Red Hat Enterprise Linux 9 (x86\_64, ARM64, PPC64LE)
* Red Hat Enterprise Linux 10 (x86\_64, ARM64)
* Rocky Linux 8 (x86\_64, ARM64)
* Rocky Linux 9 (x86\_64, ARM64)
* Rocky Linux 10 (x86\_64, ARM64)
* 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](https://mariadb.com/engineering-policies) for details.

## Installation Instructions <a href="#installation-instructions" id="installation-instructions"></a>

* [Deploy MariaDB Enterprise with Repositories](https://app.gitbook.com/s/SsmexDFPv2xG2OTyO5yV/server-management/install-and-upgrade-mariadb/installing-mariadb/binary-packages/mariadb-package-repository-setup-and-usage)
* [Deploy MariaDB Enterprise with Package Tarballs](https://app.gitbook.com/s/SsmexDFPv2xG2OTyO5yV/server-management/install-and-upgrade-mariadb/installing-mariadb/binary-packages/package-tarballs)
* [Deploy MariaDB Enterprise with Docker](https://app.gitbook.com/s/SsmexDFPv2xG2OTyO5yV/server-management/automated-mariadb-deployment-and-administration/docker-and-mariadb/deploy-mariadb-enterprise-server-with-docker)

## Upgrade Instructions

* [Upgrade to MariaDB Enterprise Server 11.4](https://app.gitbook.com/s/SsmexDFPv2xG2OTyO5yV/server-management/install-and-upgrade-mariadb/installing-enterprise-server/upgrade-paths/mariadb-enterprise-server-11.4/upgrade-to-mariadb-enterprise-server-11.4)
* [Upgrade from MariaDB Community Server to MariaDB Enterprise Server 11.4](https://app.gitbook.com/s/SsmexDFPv2xG2OTyO5yV/server-management/install-and-upgrade-mariadb/installing-enterprise-server/upgrade-paths/mariadb-enterprise-server-11.4/upgrade-from-mariadb-community-server-to-mariadb-enterprise-server-11.4)

<sub>*This page is: Copyright © 2025 MariaDB. All rights reserved.*</sub>

{% @marketo/form formid="4316" formId="4316" %}