14-day MaxScale Trial: Explore the latest version of our advanced database proxy!
Start Trial
Download MariaDBContact Us

Release Notes for MariaDB Enterprise Server 10.5.28-22

MariaDB Enterprise Server 10.5.28-22 is a maintenance release of MariaDB Enterprise Server 10.5. This release includes a variety of fixes.

MariaDB Enterprise Server 10.5.28-22 was released on 19 Mar 2025.

Fixed Security Vulnerabilities

CVE (with cve.org link)

CVSS base score

CVE-2025-21490

4.9

Changes in Storage Engines

  • This release incorporates MariaDB ColumnStore engine version 5.6.9.

Notable changes

  • Galera protocol versions are now shown by show status - change available with installation of galera library 26.4.21+ (MDEV-35505)

  • Galera updated to 26.4.21

    • NOTE: Includes increasing the GCS protocol version, which prevents downgrades of individual nodes in the cluster as soon as all nodes have been updated

Issues Fixed

Can result in data loss

  • Fix incorrect writing of timestamp into binary log, causing discrepancy upon binlog replaying (MDEV-31761)

  • Fix trigger created with "CREATE TRIGGER table1_after_insert AFTER INSERT" which is adding rows to another table using "FOR EACH ROW insert into table2(id, name) values (NEW.id, NEW.name);" that did not work correctly when if bulk inserts are used by the application. Only the first row of the bulk insert would be added to the table (MDEV-34958)

  • History is now stored on the same partitions on different Galera nodes when system versioning is enabled (MDEV-35096)

  • Fix assertion falilure and possible index corruption with unique key and nopad collation without DESC or HASH keys (MDEV-30111)

Can result in hang or crash

  • Fix client crash the command after client sets character set to utf32 (MDEV-34090)

  • Fix possible crash where server could not construct a geomery object from the input (MDEV-33987)

  • Fix possible Spider thread hang in 'Update' state on 2nd INSERT (MDEV-35064)

  • After changing the table definition for the system table 'mysql.servers', a following execution of CREATE SERVER would previously lead to a server crash. (MDEV-33783)

    • NOTE: System tables should never be modified by a user anyhow

  • Fix sporadic failure of async replication on Galera async replica nodes with parallel replication enabled (MDEV-35465)

  • Fix possible failure of wsrep_sst_rsync SST script if user specified aria_log_dir_path different from default data directory (MDEV-35387)

  • Fix connection hang after query on a partitioned table with UNION and LIMIT ROWS EXAMINED (MDEV-35571)

  • Fix server crash in get_sort_by_table/make_join_statistics after INSERT into a view with ORDER BY (MDEV-29935)

  • Fix possible memory leak on SHUTDOWN (MDEV-35326)

  • Fix possible memory leak while shutting down server after installing the auth_gssapi plugin (MDEV-35575)

  • Fix possible crash on DELETE from a HEAP table (MDEV-22695)

  • Fix possible server crash when using INSERT DELAYED on tables with virtual columns. (MDEV-26891)

  • Fix possible crash during index traversal using tree_search_next. (MDEV-28130)

  • Fix possible hang or crash during InnoDB purge with HASH indexes during ALTER TABLE (MDEV-25654)

  • Fix possible Spider crash or hang when the first byte of a connection key is changed (MDEV-34849)

  • Fix possible runtime error caused by XA RECOVER applying a zero offset to a null pointer (MDEV-35549)

  • Fix assertion failure on cascading foreign key update of table with vcol index in parent (MDEV-29182)

  • Fix assertion failure where CURRENT_USER was not correctly copied during condition pushdown (MDEV-35090)

  • Fix cluster node hang during shutdown if threadpool is used (MDEV-35710)

  • Calling a stored routine that executes a join on three or more tables and referencing not-existent column name in the USING clause could previously result in a crash on its second invocation. (MDEV-24935)

  • Fix possible assertion failure when Galera cluster is in 'split-brain' state due to loss of communication between nodes (fix requires Galera library 26.4.21+) (MENT-2175)

  • In rare cases, an ALTER TABLE or other operation could previously hang when using NBO mode on a cluster with very low network latencies (for example, when both nodes are running on the same physical machine) (MENT-2215)

  • MariaDB Cluster and ALTER INPLACE running in Total Order Isolation (wsrep_OSU_method=TOI) now correctly abort a DML INSERT operation in InnoDB (MDEV-33064)

  • Fix possible crash in wsrep_check_sequence (MDEV-33245)

Can result in unexpected behaviour

  • Fix sporadic reporting of success when a deadlock error occurs under --ps-protocol BF aborted transaction (MDEV-35446)

  • Fix rare cases where binlog entries could receive incorrect timestamps on secondary nodes of a Galera cluster, potentially impacting replication accuracy (MDEV-35157)

  • For an authentication with the ed25519 authentication plugin the password of the CREATE USER statement is now masked in the audit log (MDEV-35507)

  • MariaDB Audit now detects all DCLs forms for masking a password (MDEV-35522)

  • sql_mode='NO_UNSIGNED_SUBTRACTION' now works for multiple unsigned integers (MDEV-35651)

  • mariadb-binlog can now correctly process more than one logfile when --stop-datetime is specified (MDEV-35528)

  • Rows in table mysql.gtid_slave_pos are now correctly deleted on Galera nodes when wsrep_gtid_mode = 1 is used, which previously lead to wrong information about replica delays (MDEV-34924)

  • EXCHANGE PARTITION now works for tables with unique blobs (MDEV-35612)

  • Fix issue where functions in default values in tables with certain character sets could break SHOW CREATE and mariadb-dump (MDEV-29968)

  • Setting pseudo_thread_id to a value exceeding 4 bytes previously resulted in truncation when written to the binary log (MDEV-35646)

  • A BEFORE INSERT Trigger previously returned with error "Field 'xxx' doesn't have a default value", if a NULL value was added for a column defined NOT NULL without explicit value and no DEFAULT specified (MDEV-19761)

  • Undefined behavior could occur when attempting to perform INSERT DELAYED on a Galera cluster node. (MDEV-35852)

  • Fix issue where ON UPDATE SET NULL could not be specified on a NOT NULL column (MDEV-35445)

  • algorithm = instant can now correctly be used if a table has partitions and one tries to change a column with an index which is not the partitions key. This previously gave error "ERROR 1846 (0A000): ALGORITHM=INSTANT is not supported. Reason: ADD INDEX. Try ALGORITHM=NOCOPY" (MDEV-34813)

  • Fix issue where DROP TABLE on child and UPDATE of parent table can cause a metadata lock BF-BF conflict when applied concurrently. (MDEV-35018)

  • Can now correctly add a foreign key on a table with a long UNIQUE multi-column index that contains a foreign key as a prefix (MDEV-33658)

  • Fix possibly wrong result using a degenerated subquery (SELECT <expr>) with window function (MDEV-35869)

  • The "Failed to write to mysql.slow_log" error no longer shown without a detailed reason for the error (MDEV-20281)

  • Fix debian-start script failure when using non-standard socket path (MDEV-35907)

  • wsrep_sst_mariadb-backup.sh no longer uses --use-memory default (100MB) resulting in prepare stage which could take hours (MDEV-35749)

  • For a SPIDER engine based table a SELECT from the spider table and INSERT into a local table fails with 'Out of Range Value for Column XX_YY' Causes ERROR 1264 (22003) (MENT-2204)

Related to performance

  • Conditions with SP local variables are now pushed into derived table. Previous behaviour caused slow performance and table scans instead of using the pushed down condition (MDEV-35910)

  • NULL-aware materialization with IN predicate and single column no longer skips building sorted Ordered_key structures (MDEV-34665)

  • During an online table rebuild of an InnoDB statistics table, opt_search_plan_for_table() no longer sometimes degrades to full table scan (MDEV-35443)

Changelog

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

Platforms

In alignment to the enterprise lifecycle, MariaDB Enterprise Server 10.5.28-22 is provided for:

  • AlmaLinux 8 (x86_64, ARM64)

  • AlmaLinux 9 (x86_64, ARM64)

  • Debian 11 (x86_64, ARM64)

  • Microsoft Windows (x86_64) (MariaDB Enterprise Cluster excluded)

  • Red Hat Enterprise Linux 8 (x86_64, ARM64)

  • Red Hat Enterprise Linux 9 (x86_64, ARM64)

  • 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 20.04 (x86_64, ARM64)

  • 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

Upgrade Instructions

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

PreviousRelease Notes for MariaDB Enterprise Server 10.5.29-23NextRelease Notes for MariaDB Enterprise Server 10.5.27-21

Last updated

Was this helpful?