Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Release notes for MariaDB Enterprise Server 10.3 series releases
An overview of changes, improvements, and what's new in MariaDB Enterprise Server 10.3
MariaDB Enterprise Server 10.3 introduces the following new features:
MariaDB Enterprise Server uses an enterprise lifecycle, which provides optimized builds, predictable release behavior, and vendor support.
collects trace data to aid query optimization and diagnosis of query execution issues.
enables non-blocking backups of MariaDB Enterprise Server.
This page is: Copyright © 2025 MariaDB. All rights reserved.
MariaDB Enterprise Server 10.3.39-20 is a maintenance release of 10.3. |This release includes a variety of fixes.
MariaDB Enterprise Server 10.3.39-20 was released on 2023-06-13.
MariaDB Enterprise Server 10.3 is EOL (end-of-life) as of 2023-05-25. Users of this release series should upgrade to a more recent Enterprise Server release series.
N/A
(Medium)
#1:
MariaDB CVEs are assigned a word rating instead of a CVSS base score. See the MariaDB Engineering Policy for details.
When is set and is greater than 0, replica servers can hang if data is inserted into tables with a sequence. (MDEV-29621)
In alignment with the enterprise lifecycle, MariaDB Enterprise Server 10.3.39-20 is provided for:
CentOS 7 (x86_64)
Debian 10 (x86_64, ARM64)
Microsoft Windows (x86_64) (MariaDB Enterprise Cluster excluded)
Red Hat Enterprise Linux 7 (x86_64)
Red Hat Enterprise Linux 8 (x86_64, ARM64)
Rocky Linux 8 (x86_64, ARM64)
SUSE Linux Enterprise Server 12 (x86_64)
SUSE Linux Enterprise Server 15 (x86_64, ARM64)
Ubuntu 20.04 (x86_64, ARM64)
Some components of MariaDB Enterprise Server might not support all platforms. For additional information, see "MariaDB Corporation Engineering Policies".
This page is: Copyright © 2025 MariaDB. All rights reserved.
This ninth release of MariaDB Enterprise Server 10.3 is a hotfix release to address a CVE which has been rated "critical" using the criteria defined in the MariaDB Engineering Policy.
MariaDB Enterprise Server 10.3.25-9 was released on 2020-10-07.
CVE (with link)
CVSS base score
#1:
MariaDB CVEs are assigned a word rating instead of a CVSS base score. See the for details.
In alignment with the , MariaDB Enterprise Server 10.3.25-9 is provided for:
Red Hat Enterprise Linux 8
Red Hat Enterprise Linux 7
Red Hat Enterprise Linux 6
CentOS 8
Some components of MariaDB Enterprise Server might not support all platforms. For additional information, see "".
CentOS 6
Ubuntu 20.04
Ubuntu 18.04
Ubuntu 16.04
Debian 10
Debian 9
Debian 8
SUSE Linux Enterprise Server 15
SUSE Linux Enterprise Server 12
Microsoft Windows
N/A (Critical)#1
This first release of 10.3 includes a variety of new features and fixes, compared to MariaDB Community Server 10.3.15.
MariaDB Enterprise Server 10.3.16-1 was released on 2019-07-08.
with support for non-blocking Backups
Backup Stages for
Maximum number of secondary indexes increased to 128 per table
Slow master shutdown option
A new Enterprise config file is provided that sets optimized defaults:
Server does not load plugins of maturity Beta or lower
Authentication plugin is loaded by default
Account root is using by default on Linux systems
Accounts for root can only connect from the local host
plugin, used by MariaDB MaxScale, is now of maturity stable
Access to data provided by the plugin via the information schema requires the privilege
Unsupported Community plugins are not loaded by default
Embedded Server removed
In alignment with the , MariaDB Enterprise Server 10.3.16-1 is provided for:
CentOS 7
CentOS 6
Debian 9
Debian 8
Some components of MariaDB Enterprise Server might not support all platforms. For additional information, see "".
Accounts of type anonymous-user removed
Database "test" has no default grants
plugin is activated by default with settings:
Audit plugin is loaded by default, but is not activated
plugin is loaded by default on Linux systems
HeidiSQL is not included in Windows installations
Red Hat Enterprise Linux 6
Ubuntu 18.04
Ubuntu 16.04
Microsoft Windows
Redundant writes to the redo log have been removed.
The default for the plugin load option plugin-maturity is now stable
and the MariaDB Audit plugin trace now add the user who initiated statements with the DELAYED option. In previous versions a system user was added.
A table could not be loaded after an instant ALTER ... ADD COLUMN or ALTER ... DROP COLUMN, if the primary key is a column with variable-length encoding like UTF8
Primary (master) could crash when it executes and a replica (slave) reconnects having reset its connection status with the primary (e.g., CHANGE MASTER TO MASTER_USE_GTID = slave_pos).
"Out of memory" error could occur when accessing partitioned tables.
A crash could occur when ADD PRIMARY KEY was executed by a connection just after another connection issued an instant ADD COLUMN to the same InnoDB table and if DMLs were executed at the same time.
Client received error SEC_E_INVALID_TOKEN when SSL is used and connecting to MariaDB Enterprise Server running on Microsoft Windows.
The restore of tables was not always possible if was using the parameters --incremental
An incomplete result set was returned when was too small.
A query with system versioning filters did not show an error when executed on not tables.
erroneously reported error "Found a misplaced row" for system versioned tables with history partition.
None
In alignment with the enterprise lifecycle, MariaDB Enterprise Server 10.3.21-5 is provided for:
Red Hat Enterprise Linux 8
Red Hat Enterprise Linux 7
Red Hat Enterprise Linux 6
CentOS 8
CentOS 7
CentOS 6
Ubuntu 18.04
Ubuntu 16.04
Debian 10
Debian 9
Debian 8
SUSE Linux Enterprise Server 15
SUSE Linux Enterprise Server 12
Microsoft Windows
Some components of MariaDB Enterprise Server might not support all platforms. For additional information, see "MariaDB Corporation Engineering Policies".
MariaDB Enterprise Server 10.3.36-17 is a maintenance release of 10.3. This release includes a variety of fixes.
MariaDB Enterprise Server 10.3.36-17 was released on 2022-09-12.
CVE (with link)
CVSS base score
Debian 9 support has been discontinued.
The has been added for with a default value of 0. ()
When is executed with the command-line option, the backup tries to copy the InnoDB buffer pool dump file, which is located at the path defined by the . ()
Starting with this release, only copies the InnoDB buffer pool dump file during State Snapshot Transfers (SSTs) for MariaDB Enterprise Cluster, powered by Galera.
When is executed against an encrypted InnoDB tablespace file, the table can be corrupted. ()
When INSERT .. SELECT .. GROUP BY is executed, and the GROUP BY clause contains a derived table, the server can crash. ()
When a query contains an ANY(SELECT .. GROUP BY(SELECT ..)) predicand with a redundant subquery in the GROUP BY clause, the server can crash. ()
When is used to add a column with the INSTANT
For multi-table [UPDATE|[UPDATE]] or queries, the optimizer fails to apply partition pruning optimization for the table that is updated or deleted from. ()
When an IN condition contains a mixture of numeric and string values, results can be inconsistent. ()
When a sequence event is written to the binary log with , the value of is not respected. ()
Starting with this release, a LOST_EVENTS incident is only written to the binary log when safe rollback is not possible.
When a replica server replicates an incident event, the details about the failure are not in the primary server's error log, the replica server's error log, or the output of . ()
When a backup is performed with , the backup includes binary logs. ()
When uses EditLine instead of readline (such as on Debian and Ubuntu), Unicode characters are not accepted. ()
When the optimizer chooses a semi-join optimization for a subquery, the LooseScan and FirstMatch strategies are not considered for certain queries where they would be appropriate, and they are considered for certain queries where they would be inappropriate. ()
When a FULLTEXT search is performed on an InnoDB table, the results are incorrect when the search term contains an apostrophe ('). (
mariadb-backup command-line option removed
mysql command-line option added
mysqldump command-line option added
In alignment with the , MariaDB Enterprise Server 10.3.36-17 is provided for:
CentOS 7 (x86_64)
Debian 10 (x86_64, ARM64)
Microsoft Windows (x86_64)
Red Hat Enterprise Linux 7 (x86_64)
Some components of MariaDB Enterprise Server might not support all platforms. For additional information, see "".
This page is: Copyright © 2025 MariaDB. All rights reserved.
MariaDB Enterprise Server 10.3.32-14 is a maintenance release of MariaDB Enterprise Server 10.3. This release includes a variety of fixes.
MariaDB Enterprise Server 10.3.32-14 was released on 2021-12-13.
Galera updated to 25.3.35
no longer enables pushdown of UDFs and Stored Functions to the Data Node by default: ()
The default value of has changed from -1 to 0
, powered by Galera, can crash on if the table does not have a primary key and if the data for a field exceeds 4096 bytes. ()
When an InnoDB tablespace (.ibd) file is imported using without a corresponding .cfg``file, InnoDB causes a server crash. ([MDEV-26131](https://jira.mariadb.org/browse/MDEV-26131), [MDEV-20931](https://jira.mariadb.org/browse/MDEV-20931))
When (or ) is executed against an InnoDB table with a FULLTEXT index, InnoDB can cause a server crash. (, MENT-1198)
does not prevent replication. ()
joiner node incorrectly uses localhost for TLS certificate verification and fails to join cluster when and encrypt=3 are configured. ()
is not able to replay some outputs if 0 is in the data. ()
In alignment with the , MariaDB Enterprise Server 10.3.34-15 is provided for:
CentOS 7 (x86_64)
CentOS 8 (x86_64, ARM64)
Debian 9 (x86_64, ARM64)
Debian 10 (x86_64, ARM64)
Some components of MariaDB Enterprise Server might not support all platforms. For additional information, see "".
This page is: Copyright © 2025 MariaDB. All rights reserved.
This third release of 10.3 is a maintenance release, including a variety of fixes.
MariaDB Enterprise Server 10.3.18-3 was released on 2019-09-30.
Due to a race condition in InnoDB, an exclusive lock to an inserted record could be wrongly granted to multiple transactions when the transaction commits. This could lead to a server crash or data loss. ()
INSERT...ON DUPLICATE KEY UPDATE, when there is more than one key, could result in inconsistent data between master and slave for replication mode and . This has been fixed for but cannot be controlled by the replication for based replication.
Inconsistent Slaves need to be set up again from the Master. ()
Replication could hang for transactions, as has its own concurrency control . ()
Fix potential crash in ON UPDATE CASCADE when the foreign table is . ()
After setting SET it is possible to drop indexes from referenced (parent) tables, which could cause to behave as if the table doesn't exist in the engine ()
Fix for the corner case where could fail because encrypted data files could not be copied if created shortly before the backup was started. ()
could fail in the prepare phase if the redo log is bigger than 512GB. ()
Optimized scanning of the undo log versions while scanning the secondary index versions. ()
system variable added
command-line option added
In alignment with the , MariaDB Enterprise Server 10.3.18-3 is provided for:
CentOS 8
CentOS 7
CentOS 6
Debian 10
Some components of MariaDB Enterprise Server might not support all platforms. For additional information, see "".
ROW_FORMAT.frmFor tables created prior to MariaDB Server 10.2, the ROW_FORMAT in the .frm file could be inconsistent with the actual row format used by the data file. If the server were upgraded to MariaDB Enterprise Server 10.6, the inconsistency could remain.
When INSERT .. SELECT is executed, and the SELECT query calls an aggregate or window function, the server can crash with a segmentation fault. (MDEV-26427)
When the is called, the server can crash with a segmentation fault. (MDEV-29188)
When a query uses the DISTINCT keyword and calls an aggregate function as an argument for an always-constant function, the server can crash. (MDEV-23809)
An always-constant function is a function that always returns a constant value, even if the function's arguments are not constant.
For example, the is an always-constant function.
When is executed with the and options, the backup can hang due to a race condition between threads. (MDEV-29043)
When an EXISTS predicate or an IN, ALL, or ANY predicand is used in an eliminated GROUP BY clause, the server can crash. (MENT-1606, MDEV-29350)
When a transaction can't be fully written to the binary log, but the transaction can be safely rolled back, a LOST_EVENTS incident event is written to the binary log. (MDEV-21443)
In previous releases, this problem could cause replica servers to encounter the following error:
Starting with this release, the CTE calculation is aborted when the calculated values do not fit in the column types. When this occurs, a warning or error (depending on is raised with the error code and the following error message:
Starting with this release, when a search term contains an apostrophe ('), InnoDB tokenizes the word at the apostrophe, ignores the first token, and matches against the second token.
Rocky Linux 8 (x86_64, ARM64)
SUSE Linux Enterprise Server 12 (x86_64)
SUSE Linux Enterprise Server 15 (x86_64, ARM64)
Ubuntu 18.04 (x86_64, ARM64)
Ubuntu 20.04 (x86_64, ARM64)
7.5
6.5
6.5
In previous releases, Enterprise Spider pushed UDFs and Stored Functions down to the Data Node by default, which could cause query results to be inconsistent.
Starting with this release, all UDFs and stored functions are evaluated on the Spider Node by default. If desired, pushdown of UDFs and Stored Functions can be explicitly enabled by setting spider_use_pushdown_udf=1. Testing is recommended to confirm that query results are consistent.
provide descriptions of each column in the COMMENT column option. (MDEV-25325)
Resolving aggregate functions that are used in a view can cause in a crash. (MDEV-24454)
Executing under can cause in a crash. (MDEV-23391)
If two InnoDB tables have a and an operation cascades from the parent table to the child table, an index on a virtual generated column in the child table can become corrupt. (MDEV-26866)
MariaDB Enterprise Cluster, powered by Galera, crashes with errors like: [ERROR] WSREP: Trx 236236 tries to abort slave trx 236238 (MDEV-25835)
Server crashes when a table uses a sequence as a column default (DEFAULT NEXT_VALUE(my_seq)) and the table is used concurrently by both a prepared statement and a normal statement. (MDEV-22785)
MariaDB Enterprise Cluster can crash due to an incorrect conflict resolution on multi-master setup. (MDEV-25992, MDEV-25114)
Memory leak with row-based replication can lead to high memory usage on replica servers. (MDEV-26712)
and generate invalid SQL for some complex views. (MDEV-26299)
When statement-based or mixed replication is used and a DML statement encounters an error in a transaction that creates or drops a temporary table, non-committed writes to transactional tables can be incorrectly replicated to replica servers. (MDEV-26833)
MariaDB Enterprise Cluster joiner node fails to join cluster when and is configured. (MDEV-26211)
does not work correctly for UDF and stored functions if used in a query's WHERE conditions. (MDEV-26545)
On a partitioned table, result of wrongly depends on the partition targeted by the previous SELECT (MDEV-26333)
If an INVISIBLE column has a computed default value, an statement that doesn't specify a value for the column causes the default value to be ignored. (MDEV-25891)
Red Hat Enterprise Linux 7 (x86_64)
Red Hat Enterprise Linux 8 (x86_64, ARM64)
SUSE Linux Enterprise Server 12 (x86_64)
SUSE Linux Enterprise Server 15 (x86_64, ARM64)
Ubuntu 18.04 (x86_64, ARM64)
Ubuntu 20.04 (x86_64, ARM64)
7.5
7.5
6.5
5.5
5.5
Basic 3-way join queries are not parsed. (MDEV-19421)
Debian 8
Red Hat Enterprise Linux 8
Red Hat Enterprise Linux 7
Red Hat Enterprise Linux 6
Ubuntu 18.04
Ubuntu 16.04
Microsoft Windows
This sixth release of 10.3 is a maintenance release, including a variety of fixes.
MariaDB Enterprise Server 10.3.22-6 was released on 2020-03-02.
CVE (with link)
* CVSS base score
The systemd start and stop timeout for the MariaDB service is now set to 900 seconds (15 minutes). ()
For (Galera Library 25.3.29):
Setting was not effective because it was done after the socket was connected or accepted. The default value also caused TCP receive buffer auto-tuning to be disabled. This led to sub-optimal performance in high-bandwidth WAN clusters. The default value for has been changed to auto, which lets the kernel tune the TCP receive buffer. A new variable with a default value of auto
During a server restart, recovery could encounter an out-of-memory condition. A restart was only possible after increasing . ()
On a rollback of a large insert or update, or during a background task to purge transaction history after a large update or delete, the server could hang. ()
On a rollback or during a background task to purge transaction history due to a SPATIAL INDEX, the server could hang. ()
Executing or on tables could lead to an unexpected SQL Error (1118): Row size too large, when (default). ()
Queries that use window functions and implicit grouping could return wrong results. ()
Queries which use DISTINCT COUNT(*) OVER() in the expression returned wrong results. ()
Server could not be started when is set in a config file. (MENT-625)
None
In alignment with the , MariaDB Enterprise Server 10.3.22-6 is provided for:
Red Hat Enterprise Linux 8
Red Hat Enterprise Linux 7
Red Hat Enterprise Linux 6
CentOS 8
Some components of MariaDB Enterprise Server might not support all platforms. For additional information, see "".
Last_SQL_Errno 1590
Last_SQL_Error The incident LOST_EVENTS occurred on the master. Message: error writing to the binary logOut of range value for column 'COLUMN_NAME' at row ROW_NUMALTER TABLE ... IMPORT TABLESPACE (MDEV-21513)Possible server crash if (default) is set and if the value for parameter pos in does not point to the beginning of an event in the binary log. (MDEV-18046)
A replication primary (master) running in semi-sync mode could crash when is executed, and the replica reconnects using the GTID protocol. (MDEV-19376)
could encounter a deadlock if a backup is taken from a replica with slave-parallel-threads is set to a value greater than 0 (MDEV-21255)
could crash when used in combination with FLUSH TABLES``and``UNLOCK TABLES``(MENT-438)
The aria_pack utility crashed when running an offline datafile compression on a table. (MDEV-14183)
Dropping a partition with and SESSION caused the MariaDB Enterprise Cluster (Galera) node to hang. (MDEV-21189)
With active optimizer trace (optimizer_trace='enabled=on') server could crash or the data of the optimizer trace could become corrupted. (MENT-614)
Inefficient thread handling in the thread pool, impacting any application that uses the thread pool. (MDEV-21343)
The MariaDB Enterprise Server config file mariadb-enterprise.cnf was not registered as a config file in RPM packages. (MENT-591)
ALTER USER IF EXISTS generated a SQL syntax error. (MENT-643)
A query using GROUP BY with an expression containing a field of a view could return wrong results. (MDEV-20922)
Running the script mysql_tzinfo_to_sql for MariaDB Enterprise Cluster could result in inconsistent timezone information across different nodes. (MDEV-21209)
Using the option with would cause it to run out of memory. (MDEV-20679)
For MariaDB Enterprise Cluster (Galera Library 25.3.29):
GCS delivered a JOIN message even if the node was in a DONOR state.
GCache could contain mixed histories from different clusters.
GComm socket timestamping/liveness checking produced false positives during replication of large transactions, which caused excessive amounts of broken connections.
Large transactions were able to monopolize bandwidth when segmentation was configured, causing delays in messages relayed by the segment representative. The fix implements fair queuing of messages.
Due to a bug in quorum computation, two primary conflicting components were formed when the group merged and partitioned again while the new primary view was forming.
A range plan was not always used for multi-join queries. (MDEV-21383)
CentOS 6
Ubuntu 18.04
Ubuntu 16.04
Debian 10
Debian 9
Debian 8
SUSE Linux Enterprise Server 15
SUSE Linux Enterprise Server 12
Microsoft Windows
5.9
6.5
6.5
4.4
New option innodb_change_buffer_dump added to Debug builds. This option dumps the contents of the change buffer to the server error log at startup. This is useful when a slow shutdown cannot be performed successfully. (MDEV-20864)
Eliminated unnecessary logging of warnings to the error log regarding maximum row size for DML statements, which should be present only for DDL operations. (MENT-454)
... could overwrite binary logs if certain conditions were present. (MDEV-20703) Conditions that must be present to trigger this bug:
mariadb-backup is executed on the MariaDB Server host, and
Configuration files from the master are used, and
Configuration files enable binary logging
If unable to upgrade to MariaDB Enterprise Server 10.3.20-4, where this bug is fixed, a workaround is available: use the --defaults option to to avoid the bug-triggering conditions by specifying a different configuration file.
Prior removal of a `#FULLTEXT
Removal of a `#FULLTEXT
Change to an table containing a `#FULLTEXT
Removal of a virtual column used by an index can result in a crash. (MENT-434)
, or on an table can cause the Server to become unresponsive. (MDEV-20852)
INSTANT ADD COLUMN on an table, which includes a FOREIGN KEY definition can result in a crash. (MENT-435)
Unnecessary logging of warnings to the error log regarding maximum row size for DML statements, which should be present only for DDL operations. (MENT-454)
After server restart, a SELECT using a #FULLTEXT
and MariaDB Backup, when using mbstream, recreated xtrabackup_info in the same directory as the backup file. Repeated extraction of the backup could fail. (MDEV-18438)
mysqld_multi.sh script could not be launched and returned a syntax error. (MENT-433)
Though not supported on Microsoft Windows, the server_audit_output_type system variable for the Audit plugin accepted a SYSLOG value. (MDEV-19851)
FOREIGN KEY constraints have been ignored during DELETE when the parent table is . ()
DELETE from the child table with a FOREIGN KEY was not possible when the table is . ()
Installing MariaDB Enterprise Server from the repository failed on CentOS 7 due to package dependencies. (MENT-420)
WARN_INNODB_PARTITION_OPTION_IGNORED error code added
In alignment with the enterprise lifecycle, MariaDB Enterprise Server 10.3.20-4 is provided for:
CentOS 8
CentOS 7
CentOS 6
Debian 10
Debian 9
Debian 8
Red Hat Enterprise Linux 8
Red Hat Enterprise Linux 7
Red Hat Enterprise Linux 6
SUSE Linux Enterprise Server 15
SUSE Linux Enterprise Server 12
Ubuntu 18.04
Ubuntu 16.04
Microsoft Windows
Some components of MariaDB Enterprise Server might not support all platforms. For additional information, see "MariaDB Corporation Engineering Policies".
MariaDB Enterprise Server 10.3.37-18 is a maintenance release of 10.3. This release includes a variety of fixes.
MariaDB Enterprise Server 10.3.37-18 was released on 2022-12-21.
The view shows details about the InnoDB temporary tablespace, which is the tablespace where InnoDB temporary tables are stored. (MDEV-29479)
Starting with this release, the details about the InnoDB temporary tablespace can be shown by querying for the name innodb_temporary:
When a table's default collation is set to the default collation for the table's character set, shows the COLLATE clause. ()
In previous releases, MariaDB Enterprise Server reduced the size of SHOW CREATE TABLE output by excluding the COLLATE clause if the table's default collation was set to the default collation for the table's character set.
When a column is renamed in a partitioned table with using the , the table can be corrupted. ()
When the InnoDB storage engine performs change buffer operations, the I can overflow, which can cause table corruption. (MENT-1661, )
When a query contains an IN/ALL/ANY predicand and the subquery contains a GROUP BY clause with an IN/ALL/ANY predicand with a single-value subquery as the left operand, the server can crash. ()
If an InnoDB table contains a foreign key constraint and the child table's DATABASE_NAME/TABLE_NAME.ibd is longer than 330 characters, when the parent table is renamed, the server can crash. ()
When the global value of the is changed dynamically on a node that does not have MariaDB Enterprise Cluster (powered by Galera) configured, the server crashes when DDL is executed in TOI mode. ()
In previous releases, the following statements could cause a crash on a node without an Enterprise Cluster configured:
In the presence of replication filters, revoking privileges from a non-existing user on a primary (master) breaks replication on the replica (slave). ()
When is set on a replica node, the replica node does not skip replicated . ()
When a Spider table has a prefix index, query results can be incorrect. ()
InnoDB can extend tablespace files when additional capacity is not required. (
When an InnoDB table contains virtual generated columns that are indexed, InnoDB fails to purge secondary index records. ()
When using the InnoDB adaptive hash index, non-locking reads can return wrong results due to a potential ACID violation. (, , )
When is used on a temporary table, an empty result set is returned. ()
When a sequence is used as the default value in a table, rows inserted by an
When MyRocks is installed from a Debian package, the rocksdb.cnf configuration file gets installed to /etc/mysql/mariadb.conf.d/ instead of /etc/mysql/conf.d/. ()
In alignment with the , MariaDB Enterprise Server 10.3.37-18 is provided for:
CentOS 7 (x86_64)
Debian 10 (x86_64, ARM64)
Microsoft Windows (x86_64) (MariaDB Enterprise Cluster excluded)
Red Hat Enterprise Linux 7 (x86_64)
Some components of MariaDB Enterprise Server might not support all platforms. For additional information, see .
This page is: Copyright © 2025 MariaDB. All rights reserved.
When renaming a table to a long name, the server can crash. (MDEV-29258)
When an causes InnoDB to rebuild a table with a spatial index, the server can crash. (MDEV-29520)
When an InnoDB temporary table contains a spatial index, the server can crash if the temporary table is dropped due to DROP TEMPORARY TABLE or client disconnect. (MDEV-29507)
When querying a partitioned table using the PARTITION syntax, if the WHERE clause results in an index merge, the server can crash. (MDEV-21134)
When detecting CTE dependencies of nested CTEs that include one or more recursive CTEs, infinite recursion can occur until the server crashes. (MDEV-29361)
When the is configured to use the bundled wsrep_notify.sh script, the server can hang during startup. (MDEV-27682)
When selecting from InnoDB's (such as , , and ), if connections with open XA transactions are disconnected or killed at the same time, the server can crash. (MDEV-29575)
For some queries that involve tables with different but convertible character sets for columns taking part in the query, a repeatable execution of such queries in the prepared statement mode or as part of a stored routine can crash the server. (MDEV-16128)
When executing a SELECT .. UNION .. SELECT or statement, the server can crash. (MDEV-23160)
When ' is set and a view that includes a subquery is queried, the server crashes. (MDEV-16549)
When the rolling upgrade procedure for MariaDB Enterprise Cluster (powered by Galera) is used to upgrade from ES 10.3 to ES 10.4, the joiner nodes can crash after the upgrade to ES 10.4. (MDEV-29375)
In previous releases, the MariaDB Error Log on the joiner node could contain the following error about the crash:
When an InnoDB table is being rebuilt, and a is updated during the online rebuild, a memory leak can occur. (MDEV-29600)
When a view is queried using a prepared statement, the query fails with the error code. (MDEV-17124)
In previous releases, the following error would occur:
INSERT ... SELECTWhen a column has both a and a , full-text search using MATCH(..) AGAINST(..) does not work properly. (MDEV-29778)
If the server is started with the enabled, but the TLS certificates and keys are not configured, the server will advertise the TLS support in the handshake but will not actually be able to use it. (MDEV-29811)
With MariaDB Enterprise Cluster, when is configured, the joiner node ignores custom values for the system variable, and the SST copies the buffer pool file to the default location instead. (MDEV-28968)
Rocky Linux 8 (x86_64, ARM64)
SUSE Linux Enterprise Server 12 (x86_64)
SUSE Linux Enterprise Server 15 (x86_64, ARM64)
Ubuntu 18.04 (x86_64, ARM64)
Ubuntu 20.04 (x86_64, ARM64)
MariaDB Enterprise Server 10.3.38-19 is a maintenance release of MariaDB Enterprise Server 10.3. This release includes a variety of fixes.
MariaDB Enterprise Server 10.3.38-19 was released on 2023-03-13.
When executing a DELETE or UPDATE with a subselect, the server can crash. ()
When performing an incremental backup, MariaDB Enterprise Backup does not reflect databases that have been dropped and created. ()
When DELETE HISTORY is executed for a system versioned table with full text index, the server can crash. ()
When an ALTER TABLE statement causes InnoDB to rebuild a table with a spatial index, the server can crash. ()
When using SPIDER with SPIDER_DIRECT_SQL and spider_udf_ds_use_real_table=1
log_query_not_using_indexes=OFF is ignored when log_slow_filter is an empty string. ()
MariaDB Enterprise Backup returns with an error when the option --galera-info is used for creating a backup of a MariaDB Server instance, which is not a MariaDB Enterprise Cluster node. Failed to get master wsrep state from SHOW STATUS ()
When querying a table with virtual generated columns using full text search, these columns are not generated and are always
In alignment with the , MariaDB Enterprise Server 10.3.38-19 is provided for:
CentOS 7 (x86_64)
Debian 10 (x86_64, ARM64)
Microsoft Windows (x86_64) (MariaDB Enterprise Cluster excluded)
Red Hat Enterprise Linux 7 (x86_64)
Some components of MariaDB Enterprise Server might not support all platforms. For additional information, see .
This page is: Copyright © 2025 MariaDB. All rights reserved.
SELECT * FROM information_schema.INNODB_SYS_TABLESPACES
WHERE name LIKE 'innodb_temporary';[Note] WSREP:
####### Assign initial position for certification: 5c410a36-23a8-11ed-a44c-f6f37823dd10:3, protocol version: -1
[ERROR] WSREP: Corrupt buffer header: addr: 0x7f722bd5b530, seqno: 7019267256999739392, size: 825111097, ctx: 0x559652a28678, flags: 14391. store: 46, type: 49
[ERROR] mysqld got signal 6 ;SET GLOBAL wsrep_on=ON;
CREATE TABLE t (c INT) ENGINE=InnoDB;ERROR 1615 (HY000): Prepared statement needs to be re-preparedWhen executing REPLACE INTO ... PARTITION(...), the server can crash. (MDEV-29636)
Galera SST doesn't properly handle undo* files from InnoDB. As a result, SST may terminate incorrectly when --innodb-undo-tablespaces is set to 3 or more. (MDEV-30157)
With a query containing nested WINDOW clauses, the server can crash. (MDEV-30052)
When executing a SELECT from complex a view with WHERE clause and with the setting derived_merge=on, the server can crash. (MDEV-30081)
Infinite sequence of recursive calls when processing embedded CTE, when such a reference has the same table name as the name of the CTE. (MDEV-30248)
A deadlock between InnoDB statistics updates and BLOB insert can result in a server hang. (MDEV-29883)
NULLIdentifiers are not quoted for the output of SHOW GRANTS. Using the result to execute the grant statement results in a syntax error, if reserved keywords are used. (MDEV-30056)
Spider table with CHARSET utf32/utf16/ucs2 tries to set client CHARSET to unsupported value. (MDEV-29562)
Incorrect results are returned when using STDDEV_SAMP() with a view. (MDEV-19071)
A spurious error can be generated: ERROR 1292 (22007) at the line 15: Truncated incorrect DECIMAL value:#(MDEV-30342)
When running mariadb-binlog using the option --verbose, cannot read row events with compressed columns: Error: Don't know how to handle column type:... (MDEV-25277)
Incorrect results are returned with outer join, merged derived table, and view. (MDEV-28602)
Some DDL, such as ANALYZE, can be completed out of order on parallel replicas. (MDEV-30323)
seconds_behind_master is incorrect for delayed parallel replicas. (MDEV-29639)
Rocky Linux 8 (x86_64, ARM64)
SUSE Linux Enterprise Server 12 (x86_64)
SUSE Linux Enterprise Server 15 (x86_64, ARM64)
Ubuntu 18.04 (x86_64, ARM64)
Ubuntu 20.04 (x86_64, ARM64)
#1:
MariaDB CVEs are assigned a word rating instead of a CVSS base score. See the MariaDB Engineering Policy for details.
The new --system={all, users, plugins, udfs, servers, stats, timezones} command-line option allows dumping system information in logical form. (MDEV-23630)
Added primary host and port info to replica stop messages. (MDEV-10272)
Parameter has no effect and is defined as deprecated. (MDEV-24536)
New to continue the backup process when corruption is encountered. Corrupted pages are logged in the backup_corrupted file in the backup destination directory. ()
adds completed with Error! to the end of the log file if the backup is started with the parameter and completed with corrupted tables. The new log entry canceled with an Error! will be used when the backup cannot not be completed. (MENT-1059)
and system variables are read-only. ()
In a very unlikely event, corruption of the system tablespace or the last recovered page can occur on recovery or a (MENT-1124, MDEV-24449)
Crash on recovery after server kill during instant ADD COLUMN (MDEV-24323)
Possible segfault on CREATE TABLE with explicit FTS_DOC_ID_INDEX using multiple fields. (MDEV-24403)
Server crashes upon attempt to update the view through the second execution of a stored procedure. (MDEV-16940)
containing a clause can crash. (MDEV-22781)
Possible crash for a query using recursive CTE without having a default schema defined. ()
Server crash on WITH RECURSIVE UNION ALL (CTE) query. ()
Server hangs due to Galera lock conflict resolution. ()
Possible crash in replication when applying a transaction that contains cascading foreign key delete for a table, and that has an indexed virtual column. ()
Possible lock conflicts between two wsrep high priority threads in on tables having unique secondary keys. ()
Server crash when uses a subselect. ()
Possible crash of the server when audit logging is active. (MENT-1098)
is missing the WITH GRANT privilege for roles. (MDEV-24289)
mysqld_safe log messages are missing in the error log file. (MDEV-21367)
CHECK_CLAUSE field in truncates check constraint expressions. (MDEV-24139)
Unexpected error message when selecting from a view that uses a mergeable derived table. ()
Permission denied error message is returned to users with permissions for nested CTEs. ()
Regression: SELECT .. UNION .. with inconsistent column names fails. ()
Race condition between and transaction commit with . ()
Plugin system variables and activation options can break for . ()
SELECT INTO OUTFILE used permission 666 where 644 should be used to limit the privileges to change the file. ()
Syntax error on correct syntax for that includes X is null = 0 ()
Altered connection limits for the user have no effect. ()
Syntax error when using COLLATE for creating virtual columns. ()
Auto purge of relaylogs stops when relay-log-file is slave-relay-log.999999 and is enabled. ()
ORDER BY in the view definition leads to a wrong result with GROUP BY on the query using the view. ()
column from a derived table returns invalid values. ()
doesn't respect filters for PROXY_CONNECT events. ()
plugin doesn't consider proxy users in and ()
With the ALTER USER .. IDENTIFIED BY command, the password isn't replaced by asterisks in the audit log. (MENT-1128)
Queries against tables return wrong values for columns following constant declarations. Fix backported from 10.4.13 ()
does not insert a history row for or application period-based tables if the row has not changed. ()
Wrong duplicate primary key error between the history row generated on referential action and the history row on evaluating foreign referential action for self-reference in a table (, )
Wrong number of decimal digits in certain UNION or subquery constellations, like the union of unsigned and NULL type. ()
CREATE TABLE .. SELECT FROM does not create table if is not using a scalar value ()
may report incorrect binlog position information after ()
Sequences, which are used as the default by a table, are not dumped in the right order by ()
fails with error messages ALGORITHM=INSTANT is not supported for this operation (MDEV-16735)
performance schema table schema changed
information schema table schema changed
performance schema table schema changed
performance schema table schema changed
performance schema table schema changed
performance schema table schema changed
performance schema table schema changed
performance schema table schema changed
system variable maximum value changed from 18446744073709551615 to 4294967295
command-line option added
command-line option added
command-line option added
command-line option added
--version command-line option added
system variable minimum value changed from 8 to 64
command-line option added
performance schema table schema changed
performance schema table schema changed
performance schema table schema changed
In alignment with the enterprise lifecycle, MariaDB Enterprise Server 10.3.28-11 is provided for:
Red Hat Enterprise Linux 7
Red Hat Enterprise Linux 8
CentOS 7
CentOS 8
Ubuntu 16.04
Ubuntu 18.04
Ubuntu 20.04
Debian 9
Debian 10
SUSE Linux Enterprise Server 12
SUSE Linux Enterprise Server 15
Microsoft Windows
Some components of MariaDB Enterprise Server might not support all platforms. For additional information, see "MariaDB Corporation Engineering Policies".
CVE (with cve.org link)
CVSS base score
N/A (Critical)
Limit to 255 (MDEV-22258)
Minimum value of raised to 8 (previously 4), so fixed-size data types like and are not truncated for lower values of . (MDEV-22715)
Backport from MariaDB Server 10.5.4 improvements to for InnoDB. (MENT-636)
Backport option from MariaDB Server 10.4. (MENT-581)
doublewrite recovery can corrupt data pages. (MDEV-11799)
table can disappear when trying to change the primary key after disabling Foreign Key checks and violating a Foreign Key constraint. (MENT-804)
corruption in delete buffering. (MDEV-22497)
Rollback of insert fails when column reorder happens. (MDEV-22637)
Possible data inconsistency when executing ADD PRIMARY KEY with concurrent DML transactions. ()
deadlock in (MDEV-22890)
data file extension is not crash-safe. (MDEV-23190)
is not crash-safe. (MDEV-21347)
Deadlock involving parallel workers, , and (MDEV-23089)
Crashes when running a SQL query containing a specific subquery pattern. ()
Dropping the adaptive hash index may cause DDL to lock up InnoDB. ()
TO could result in a crash when the value exceeds the max allowed 2147483647 ()
Crash on WITH RECURSIVE large query. ()
Crash with Prepared Statement with a ? parameter inside a re-used CTE. ()
MariaDB could crash after changing the query_cache size. ()
Crash in CREATE TABLE AS SELECT when the precision of the returning type = 0 ()
or in a statement, which has a 0x00 byte in one of the values, could crash the server. ()
recovery can block server startup. (MENT-915)
Service shutdown fails if the OS datetime has been updated backwards. (MDEV-17481)
ALTER TABLE .. ANALYZE PARTITION can run for hours for huge tables if engine-independent persistent statistics are enabled, due to reading and locking of all rows in the table instead of for the partition. (MDEV-21472)
can fail with a privilege error when the privilege exists at the database level, but the privilege exists at the table level. (MDEV-23010)
Latency and throughput regression identified in write-heavy benchmarks for the latest releases in MariaDB Server 10.2, 10.3, and 10.4. (MENT-909)
START SLAVE UNTIL .. file .. pos stops at an earlier position earlier than defined if the transaction that spans over the given stop position has to roll back due to conflicts. ()
mariadb-backup does not stop on errors while applying redo log. ()
Point-in-time recovery of the binary log fails with a syntax error when . ()
Replication aborts with upon CREATE .. SELECT when . ()
Regression in Audit Plugin Performance. (MENT-700)
and can't run if the library file doesn't exist. (MDEV-21258)
installation hangs the installation process. (MENT-926)
command-line option added
system variable minimum value changed from 4 to 8
command-line option added
mysql --tls-version command-line option added
command-line option added
command-line option added
command-line option added
command-line option added
command-line option added
command-line option added
command-line option added
command-line option added
system variable added
In alignment with the enterprise lifecycle, MariaDB Enterprise Server 10.3.24-8 is provided for:
Red Hat Enterprise Linux 8
Red Hat Enterprise Linux 7
Red Hat Enterprise Linux 6
CentOS 8
CentOS 7
CentOS 6
Ubuntu 20.04
Ubuntu 18.04
Ubuntu 16.04
Debian 10
Debian 9
Debian 8
SUSE Linux Enterprise Server 15
SUSE Linux Enterprise Server 12
Microsoft Windows
Some components of MariaDB Enterprise Server might not support all platforms. For additional information, see "MariaDB Corporation Engineering Policies".
CVE (with cve.org link)
CVSS base score
4.4
5.3
4.9
4.9
N/A (Medium)
#1:
MariaDB CVEs are assigned a word rating instead of a CVSS base score. See the MariaDB Engineering Policy for details.
now displays a warning when upgrading a replica from MySQL Server to MariaDB Enterprise Server if data was present in the mysql.slave_master_info and mysql.slave_relay_log_info tables. A warning is needed as this information will be ignored. (MDEV-10047)
has a new --ignore-table-data=<table> option. When used, the dump will include the table definition for the listed tables, but not the INSERT statements for the data in the table. (MDEV-22037)
has a new option. By default, mariadb-backup will not commit or rollback uncommitted XA transactions, and when the backup is restored, any uncommitted XA transactions must be manually committed using XA or be manually rolled-back using . The option can be used to rollback uncommitted XA transactions while performing a --prepare operation, eliminating the need for manual commit or rollback when the backup is restored. ()
is now limited to 255. ()
system variable added, to control that a primary server only completes the shutdown after the last binary log has been sent to all connected slaves. This behavior is not active by default. Before the addition of this system variable, this was achieved using mysqladmin shutdown --wait_for_all_slaves for a master. (MENT-202)
aria_pack tool now provides the options --datadir, --ignore-control-file, --require-control-file for tables with auto-recovery enabled (TRANSACTION=1``). (MENT-657)
system variable was added to control whether an instant ADD or DROP column or reorder can change an format. The default is add_last to allow an instant ADD COLUMN as the last column of the table. Option should never be used if a tablespace import to an older version of MariaDB Server should be possible. ()
Possible crash with data loss when executing an update of PRIMARY KEY columns on an table with a column. (MDEV-22384)
ignored the timeout setting when an explicit LOCK TABLES ... WRITE was active in another session. As a result, MariaDB Enterprise Server waited for the release of the lock even if the timeout was reached. (MDEV-20230)
When additional open_table_caches_instances have been created, a crash could occur due to exceeding the limit of open file descriptors. (MDEV-18027)
Clean shutdown of MariaDB Enterprise Cluster was not possible due to a deadlock situation between Galera Nodes. (MENT-432)
Adding a column to the discarded tablespace was possible, resulting in a crash. ()
Replication could be aborted when the replication data includes nested version-based conditional comments.
and mysqld_safe processes showed as running after a server shutdown. (MDEV-21563)
ignored the configuration from the server configuration file. (MDEV-19347)
A duplicate key error showed the duplicate key value truncated to 64 characters without indicating the truncation. ()
Using SET GLOBAL for the variables , i , , and could lead to corrupted strings for the settings. ()
Changing the Server-Id could lead to events being disabled for replicas, even if a single node configuration without a replica was used. ()
incorrectly shows the privilege Delete versioning rows instead of Delete history ()
Wrong query results have been returned with ()
does not quote role names properly for a user granted to this role. ()
Partitioning could choose the wrong partition for the RANGE partitioning by the column. ()
The plugin pam_user_map.so was not provided with binary tarball packages. (MDEV-21913)
system variable maximum value changed from 4294967295 to 255
system variable added
command-line option added
command-line option added
command-line option added
command-line option added
system variable added
In alignment with the enterprise lifecycle, MariaDB Enterprise Server 10.3.23-7 is provided for:
Red Hat Enterprise Linux 8
Red Hat Enterprise Linux 7
Red Hat Enterprise Linux 6
CentOS 8
CentOS 7
CentOS 6
Ubuntu 20.04
Ubuntu 18.04
Ubuntu 16.04
Debian 10
Debian 9
Debian 8
SUSE Linux Enterprise Server 15
SUSE Linux Enterprise Server 12
Microsoft Windows
Some components of MariaDB Enterprise Server might not support all platforms. For additional information, see "MariaDB Corporation Engineering Policies".
CVE (with cve.org link)
CVSS base score
5.5
This thirteenth release of10.3 is a maintenance release. This release includes a variety of fixes.
MariaDB Enterprise Server 10.3.31-13 was released on 2021-09-14.
CVE (with link)
CVSS base sore
This release of MariaDB Enterprise Server includes features backported from MariaDB Enterprise Server 10.6.
Enhanced consistency for Semi-Sync Replication
When , consistency is guaranteed for a Primary server in an HA (Primary/Replica) topology when using semi-synchronous replication. ()
Prior to this release, when using semi-synchronous replication, if a Primary crashed before sending a transaction to the Replica, on restart, the Primary could recover incomplete InnoDB transactions when rejoining as a Replica.
Galera updated to 25.3.34
ARM64 is now supported for several .
The script wsrep_sst_mariadb-backup checks all server-related configuration groups when processing a configuration file. ()
Prior to this release, only the [mysqld
When an statement is executed with ALGORITHM=INSTANT, a warning is not raised when the operation causes the default value of a DATE column to be truncated. ()
Possible server crash when pushing a WHERE condition over a mergeable derived table / view / CTE DT into a grouping view / derived table / CTE V whose item list contained set functions with constant arguments. ()
Server crashes on the second execution of a stored procedure or a prepared statement when the corresponding query executes a window function on a view, CTE, or derived table. ()
Server crashes are possible when executing a prepared statement with a hanging recursive CTE. ()
When fails after dropping the table, the DROP TABLE operation is not written into the binary log. ()
The statement does not quote role names properly for the DEFAULT ROLE. ()
The utility reports errors for freed pages. ()
As a result of this issue, a Joiner node writes the following error to the MariaDB Error Log:
With MariaDB Enterprise Cluster, when is set, rsync for a new SST process may be killed rather than the rsync for the old SST process. ()
With MariaDB Enterprise Cluster, the WSREP threads could write warnings about foreign keys to the MariaDB Error Log when wsrep_debug is not enabled. ()
In prior releases, the following warning could be written to the log:InnoDB: WSREP: referenced FK check fail: Lock wait index
information schema table added
information schema table added
system variable default value changed from DEFAULT to "" (empty)
In alignment with the , MariaDB Enterprise Server 10.3.31-13 is provided for:
CentOS 7 (x86_64)
CentOS 8 (x86_64, ARM64)
Debian 9 (x86_64, ARM64)
Debian 10 (x86_64, ARM64)
Some components of MariaDB Enterprise Server might not support all platforms. For additional information, see .
This page is: Copyright © 2025 MariaDB. All rights reserved.
This second release of 10.3 is a maintenance release, addressing security vulnerabilities and including a variety of fixes.
MariaDB Enterprise Server 10.3.17-2 was released on 2019-08-19.
CVE (with link)
CVSS base score
Merge relevant changes from MySQL 5.7.27
Compatibility change: Change to OFF by default
Compatibility change: Change to OFF by default
does not work with the PS protocol
Removed legacy option from enterprise build of
Changes to mysql_install_db script text
DROP TABLE IF EXISTS
--rsync option removed
option added
option added
option added
In alignment with the , MariaDB Enterprise Server 10.3.17-2 is provided for:
CentOS 7
CentOS 6
Debian 9
Debian 8
Some components of MariaDB Enterprise Server might not support all platforms. For additional information, see "".
MariaDB Enterprise Backup expects to stream a backup using the included mbstream utility. (MDEV-15730)
Prior to this release, MariaDB Enterprise Backup expected , even though the xbstream utility had been renamed to mbstream.
InnoDB no longer acquires advisory file locks by default. (MDEV-24393)
The table has been added and can be used to view details about SQL keywords. (MDEV-25129)
The table has been added and can be used to view details about built-in functions. (MDEV-25129)
When using data-at-rest encryption with the encryption plugin, InnoDB will automatically disable key rotation checks. (MDEV-14180)
The encryption plugin does not support key rotation, so key rotation checks are not required.
In previous releases, unnecessary key rotation checks with the plugin could reduce performance, unless they were explicitly disabled by setting .
Server crashes while executing a query with a recursive CTE that is indirectly used twice. (MDEV-26202)
Server crashes due to infinite recursion while processing an embedded recursive CTE with missing RECURSIVE. (MDEV-26095)
Server crashes in InnoDB deadlock checker under high load. (MDEV-25594)
Server crashes when a virtual generated column has a prefix index. (MDEV-26220)
Server crashes are possible when using virtual generated columns. (MDEV-18166, MDEV-18249)
Server crashes while executing when a column is truncated. (MDEV-17890)
Server crashes while executing when a hostname cannot be resolved. (MDEV-26081)
Server crashes when a subquery references an outer column in an ORDER BY clause. (MDEV-25629)
Server crashes due to a stack overrun in the query optimizer while executing a query with more than 32 equality conditions that compare columns of different tables (such as tableX.colX=tableY.colY). (MDEV-17783)
Server crashes when a window function is the left expression of an IN(SELECT ..) subquery. (MDEV-25630)
Possible deadlock on a Replica server using GTID Replication when and , , or is executed. (MDEV-17515)
Server crashes when fails on an InnoDB table. (MDEV-25721)
Server crashes while executing on an InnoDB table with a Full-Text Index. (MDEV-25663)
Server crashes while executing on an InnoDB table with virtual generated columns that are indexed. (MDEV-25872)
Server crashes while executing when is enabled. (MDEV-25886)
Crash when parsing query using derived table containing table value constructors (MDEV-25484)
Server crashes when a connection is killed while executing after previously locking the table with . (MDEV-17749)
Server crashes when the global value of the system variable is set using a stored function that reads the value of another global system variable. (MDEV-16481)
When an unknown column is referenced in the WHERE clause of a recursive CTE, the query sometimes succeeds instead of failing with an . (MDEV-26189)
Reusing CTE inside a function fails with the error code. (MDEV-23886)
Several fixes for MariaDB Enterprise Cluster (Galera) SST scripts. (MDEV-20580, MDEV-25818, MDEV-25759, MDEV-25719, MDEV-15639, MDEV-15371, MDEV-18797, MENT-1170, MDEV-24979, MDEV-21192)
With MariaDB Enterprise Cluster, when , MariaDB Enterprise Backup does not inherit server options set by the Environment systemd configuration parameter. (MDEV-24962)
With MariaDB Enterprise Cluster, when is set, and and/or are set to custom paths, the rsync SST does not copy the binary log index. (MDEV-25978)
table.The statement may check the wrong maximum column length. (MDEV-26203)
The storage engine handles ">=" as ">" in some cases, where multi-column indexes are used. (MDEV-25985)
The system variable does not work correctly with the authentication plugin. (MDEV-25641)
The "Condition pushdown into derived table" optimization cannot be applied if the expression being pushed refers to a derived table column, which is computed from an expression that has a stored function call, @session variable reference, or other similar construct. (MDEV-25969)
A query that uses ORDER BY .. LIMIT clause and Range checked for each record optimization could produce incorrect results. (MDEV-25858)
An aborted statement is logged in the binary log and replicated to the Replica server. (MDEV-22530)
shows an execution plan different from the plan actually executed. (MDEV-25682)
shows an execution plan different from actually executed. (MDEV-25682)
Wrong result when selecting from views, derived tables, or CTEs with the form (SELECT .. LIMIT <n>) ORDER BY .. (MDEV-25679)
For system-versioned tables, the statement displays the system-invisible row_end column as part of the primary key. (MDEV-16857)
For system-versioned tables partitioned by SYSTEM_TIME``, overflowing the partitions can lead to incorrect results from queries. (MDEV-22247)
For tables, statements that use CASE WHEN .. THEN can result in a syntax error. (MDEV-24760)
For tables, statements that use the JSON_EXTRACT() function in the WHERE clause can result in a syntax error. (MDEV-24517)
For tables, statements that call native functions using remove_str (such as ) fail with the error code. (MDEV-24020)
For tables, server-side prepared statements (created by and executed by ) incorrectly turn unsigned integer literals into signed integers. (MDEV-25808)
For tables, statements that use the function fail with the error code. (MDEV-24523)
Red Hat Enterprise Linux 8 (x86_64, ARM64)
SUSE Linux Enterprise Server 12 (x86_64)
SUSE Linux Enterprise Server 15 (x86_64, ARM64)
Ubuntu 18.04 (x86_64, ARM64)
Ubuntu 20.04 (x86_64, AM64)
Microsoft Windows (x86_64)
5.9
5.5
5.5
5.5
4.4
Merge upstream changes from (MDEV-19795)
plugin now requires the privilege to display information in the disks table in the information schema; the table will otherwise be empty (MDEV-18328)
Post-merge fixes for rocksdb.group_min_max test (MDEV-20113)
Replication hangs with "preparing" and never starts (MDEV-20247)
Failing assertion when REDO log files reach 512Gb while preparing backup (MDEV-20060)
Temporary tables created with data-at-rest encryption are not fully encrypted (MDEV-17228)
bugs related to creating tables (MDEV-19292, MDEV-20102)
for InnoDB can result in a crash in some cases (MDEV-15641)
Failing tests in buildbot related to FULLTEXT INDEX (MDEV-14154)
Server startup bug with encrypted table (MDEV-19914)
Possible crash when and foreign key is used, if the referenced record is deleted at the same time (MDEV-19660)
Recovery with crash related to InnoDB with custom innodb_data_file_path (MDEV-19978)
Add page-id matching check in tool (MDEV-19871)
DROP TEMPORARY table is logged despite no CREATE being logged in the binary log (MDEV-20091)
mysql_upgrade_service throws exception upgrading from 10.0 to 10.3 (MDEV-19427)
Loading the AUDIT plugin causes performance regression (MDEV-18661)
on table with virtual_field can cause crash (MDEV-19771)
Fix Aria ER_CRASHED_ON_USAGE and Assertion (MDEV-19595)
Test change: innodb.trx_id_future fails on 10.3+ (MDEV-20138)
Possible foreign key corruption for ALTER TABLE ... ADD COLUMN with InnoDB (MDEV-19630)
Corruption after instant ADD or DROP when the index tree shrinks (MDEV-19916)
Cannot load compressed with (MDEV-19974)
Bug in versioned tables when deleting history (MDEV-19814)
Compressed columns cannot be restored from dump (MDEV-17363)
Bugs in related to indexed virtual columns (MDEV-16222, MDEV-17005, MDEV-19870)
option added
option added
option added
option removed
option added
option added
status variable added
status variable added
status variable added
status variable added
system variable added
system variable added
system variable added
system variable added
system variable added
system variable added
system variable removed
system variable added
system variable added
Red Hat Enterprise Linux 6
Ubuntu 18.04
Ubuntu 16.04
Microsoft Windows
6.5
6.5
5.5
5.1
4.9
3.7
3.7
5.5
5.5
5.5
5.5
5.5
4.4
Galera updated to 25.3.35
The maximum values for and have been changed from 80000000 to 1099511627776 (1 TB). (MENT-1428)
Columns in some INFORMATION_SCHEMA tables are erroneously declared with DEFAULT clauses, which is not compliant with the SQL standard. (MDEV-18918)
Consequently, when sql_mode=EMPTY_STRING_IS_NULL is set, queries like CREATE TABLE .. SELECT .. FROM INFORMATION_SCHEMA... could encounter replication errors like the following:
When an statement changes the order of indexes in a MyISAM or Aria table using the INPLACE algorithm, the table can become corrupt. (MDEV-25803)
When is written to the binary log, the statement is not flagged as DDL, which causes the replica servers to execute the statement in an unsafe way if parallel replication is enabled. (MDEV-27365)
When a FULLTEXT index is added to an InnoDB table with ALGORITHM=INPLACE and the indexed column uses the tis620 character set, the server can crash with a segmentation fault (signal 11). (MDEV-24901)
When MariaDB Server is used on the ARM architecture, which uses a weak memory model, an internal hash table implementation can cause the server to crash with a segmentation fault (signal 11). (MDEV-27088)
When and are set with MariaDB Enterprise Cluster, powered by Galera, the joiner node fails to perform an SST. (MDEV-26064)
The SST log contains the following message related to the failure:
When is set, MariaDB Enterprise Backup can hang on lock acquisitions due to a deadlock. (MDEV-26558)
When a stored procedure is defined with a query that contains a set function, and the set function's only argument is an outer reference to a column of a mergeable view, a derived table, or a CTE, the second execution of the stored procedure can cause the server to crash. (MDEV-25086)
When a derived table is created for certain queries that use subqueries over Views or CTEs, the server can crash with a segmentation fault (signal 11). (MDEV-25631)
When a stored procedure uses a cursor to run a query that requires an internal temporary table (such as queries containing an ORDER BY clause), the server can crash due to a segmentation fault (signal 11). ()
Server can crash if a CTE or derived table is not used by the query. ()
When is set and a query is executed that references a derived table, the server can crash while writing the query's execution plan to the slow query log. ()
When a stored procedure or a prepared statement is used to execute a query that performs a join, which compares a GEOMETRY column with a different data type, executing the stored procedure or prepared statement twice can cause the server to crash. ()
With MariaDB Enterprise Cluster, when is set to an unknown address and is set to 0, the server crashes. ()
When a system versioned table is created with and , the server can crash. ()
When a system-versioned table is partitioned by SYSTEM_TIME, executing causes the server to crash. ()
When the following conditions are met, executing a prepared statement twice can cause the server to crash: ()
The system variable must be set to some value n.
The query must contain an IN(...) clause with more than n string literals.
The query must require character set conversions.
When a multi-byte character set is used, the last character of a column can be truncated, which makes it appear as a question mark ('?). (MDEV-24335)
Subquery using the ALL keyword on columns produces a wrong result. (MDEV-27098)
Subquery using the ALL keyword on columns produces a wrong result. (MDEV-27072)
When float literals are defined using scientific notation and the token also contains certain special characters, the parser incorrectly parses the float value and completely drops it from the request. ()
When a double-encapsulated CTE query calls a function, which reads a table that has been aliased in the CTE query, the server incorrectly raises an error with the error code. ()
When a CTE is used in a subquery of a statement, the server incorrectly raises an error with the error code. ()
When MariaDB Enterprise Cluster performs an SST, the SST scripts incorrectly try to read as a path to a directory of TLS CA certificates instead of using for that purpose. ()
When MariaDB Enterprise Cluster performs an SST, the SST scripts do not always interpret correctly. ()
When an index is used for an ORDER BY .. LIMIT query, the optimizer does not disable the Range Checked for Each Record optimization. ()
When is set, the optimizer can incorrectly choose to merge an index that does not help, because the query conditions require the full index to be scanned. ()
When the system variable is set, MariaDB Connector/C and the do not interpret MariaDB Server's extended metadata properly, which can cause results from some to be right-aligned. ()
When an INSERT .. SELECT statement selects from and inserts into the same table, rows are counted twice, which can cause row numbers to be reported incorrectly in error messages. ()
When a replica server's relay log is rotated, Seconds_Behind_Master in can temporarily show an incorrect value that is very high. ()
The collation column in the # table is incorrectly read as NULL. ()
When a join performs a comparison between an expression that uses a case-insensitive collation and an column that uses a binary collation, the comparison uses the wrong collation, which can cause results to be incorrect. ()
When is changed dynamically with , InnoDB does not enforce the minimum value that is enforced on startup, which can result in an impossibly small buffer pool with some values of . ()
When the DATABASE() function is used in some queries (such as queries using UNION ALL), database names can be truncated to 34 characters, even though database names can have up to 64 characters. ()
When the option is disabled, such as when --skip-symbolic-links or --disable-symbolic-links is set, InnoDB still allows symbolic links and .isl files to be created if tables have the DATA DIRECTORY option. ()
When CREATE TABLE t1 LIKE t2 is executed and the t2 table is a partitioned table that uses the MyISAM or Aria storage engines and has the DATA DIRECTORY option defined for partitions, the operation fails with a file system error. ()
When is set, some window functions incorrectly raise an error with the error code. ()
When a CTE is used with a UNION in a statement, the server incorrectly raises an error with the error code. ()
When the function is called with values from a subquery, the output is not always returned as the data type. ()
When a system-versioned table is partitioned by SYSTEM_TIME with a ``LIMIT` clause, can incorrectly return an error. ()
The lateral derived optimization is not disabled for queries that use WITH ROLLUP, which causes queries that use GROUP BY to return incorrect results. ()
When is set, queries that use the split optimization can return the wrong results. (, )
When a row is deleted from an InnoDB table, and then a new row with the same key is inserted into the table by a different transaction, InnoDB's MVCC code can incorrectly hide the new row from transactions that should see the changes: (MENT-1414)
Consequently, queries can try to insert another new row with the same key, which results in an error with the error code.
When a replica server has set to 'optimistic' or 'aggressive', this can result in the following error in :
error code added
system variable minimum value changed from 5242880 to 2097152
system variable dynamic changed from No to Yes
system variable maximum value changed from 80000000 to 1099511627776
system variable dynamic changed from No to Yes
system variable maximum value changed from 1600000000 to 1099511627776
mysql_upgrade command-line option added
mysqld rocksdb-ignore-datadic-errors command-line option added
system variable added
In alignment with the enterprise lifecycle, MariaDB Enterprise Server 10.3.34-15 is provided for:
CentOS 7 (x86_64)
Debian 9 (x86_64, ARM64)
Debian 10 (x86_64, ARM64)
Microsoft Windows (x86_64)
Red Hat Enterprise Linux 7 (x86_64)
Red Hat Enterprise Linux 8 (x86_64, ARM64)
SUSE Linux Enterprise Server 12 (x86_64)
SUSE Linux Enterprise Server 15 (x86_64, ARM64)
Ubuntu 18.04 (x86_64, ARM64)
Ubuntu 20.04 (x86_64, ARM64)
Some components of MariaDB Enterprise Server might not support all platforms. For additional information, see "MariaDB Corporation Engineering Policies".
This page is: Copyright © 2025 MariaDB. All rights reserved.
CVE (with cve.org link)
CVSS base score
5.5
tail: cannot open 'mysql-bin.index' for reading: No such file or directoryError 'Invalid default value for 'TABLE_NAME'' on query. Default database: 'test'. Query: 'CREATE TABLE `t1` (`TABLE_NAME` varchar(64) CHARACTER SET utf8 NOT NULL DEFAULT ''mariadb-backup: The option "innodb_force_recovery" should only be used with "--prepare".
mariadb-backup: innodb_init_param(): Error occurred.Last_Errno: 1062
Last_Error: Error 'Duplicate entry 'VALUE' for key 'KEY_NAME'' on query. Default database: 'DATABASE_NAME'. Query: 'INSERT INTO ..'This tenth release of 10.3 is a maintenance release. This release includes security fixes.
MariaDB Enterprise Server 10.3.27-10 was released on 2020-12-14.
CVE (with link)
CVSS base score
#1:
MariaDB CVEs are assigned a word rating instead of a CVSS base score. See the for details.
Galera wsrep library updated to 25.3.31 in .
In alignment with the , this release does not include CentOS 6.x and RHEL 6.x packages.
The audit plugin (not MariaDB Enterprise Audit) did not log proxy users. The new plugin version 2.0.3 introduces an event sub-type PROXY_CONNECT for event type CONNECT ()
On connect, if a proxy user is used, an extra line will be logged:
Data corruption is possible for encrypted tables if the non-default option is used. (MENT-910)
Temporary tables created by the user or the system can overwrite existing files on creation. ()
Table can disappear after ALTER TABLE command if [[]] is used before altering a child table to remove a primary key. ()
persistent stats analyze forces a full scan, which results in a lock crash. (MENT-1024)
hangs on with the error message Semaphore wait has lasted > 300 seconds. (MENT-1007)
Server crash can happen on filesort with a setting for to a value lower than the default of 64 ()
Defining a view with SQL syntax =0 incorrectly returns a syntax error. (MENT-1015)
reports an error that it cannot find an log file './aria_log.00000000' (MENT-907)
failure for incremental backups. ()
Aborting a query on an table with does not show an SQL error message if the query could not be aborted. (
mariadb_es_repo_setup curl failed on Ubuntu Focal if ca-certificates is not installed. Now it will prompt an error about missing ca-certificates (MENT-971)
system variable default value changed from ON to OFF
system variable was added
command-line option added
In alignment to the , MariaDB Enterprise Server 10.3.27-10 is provided for:
Red Hat Enterprise Linux 7
Red Hat Enterprise Linux 8
CentOS 7
CentOS 8
Some components of MariaDB Enterprise Server might not support all platforms. For additional information, see "".
TIME,HOSTNAME,user,localhost,ID,0,PROXY_CONNECT,test,plug_dest@%,0``
Better MariaDB GTID support for the option. (MDEV-19264)
New global variable (MDEV-16952)
The new parameter for the script can be used to enable a repository of unsupported packages in the repository configuration. The repository currently includes the CONNECT Storage Engine. The storage engine can be installed by yum install MariaDB-connect-engine or apt-get install mariadb-plugin-connect-engine (MENT-1003)
Back port of a MariaDB Server 10.5 feature to not acquire record locks when covering table locks exist. (MENT-403)
Change by default. (MDEV-23720)
MATCH .. AGAINST string. (MDEV-23999)mariadb-backup can hang if the server goes idle after a particular kind of redo log write. (MDEV-23982)
A server crash can occur when encryption is enabled for temporary tables (encrypt-tmp-files=ON), and queries use window functions. (MDEV-23867)
A crash of MariaDB Server is possible when binary logging is activated, caused by improper raising of an error or replication checksum. (MDEV-23832)
assertion on after ALTER TABLE .. DISCARD TABLESPACE (MDEV-23705)
Server crashes after a failed attempt to create a unique key on a virtual column. (MDEV-23685)
Possible server crash when using an index on a spatial data type with InnoDB. (MDEV-23600)
Possible server crash when a string function is used for a column of type and the string function is used in a subquery, which is returning a row. (MDEV-23535)
node can crash on high , , or load from many connections executed on the same table with foreign keys. (MDEV-23557)
Server crashes if a query is executed on an table with a foreign key where the foreign key was removed while using . This case should result in an SQL error. (MDEV-23470)
Recursive procedure call ends with a crash instead of an SQL error. (MDEV-23463)
fails to open the table during removal of VIRTUAL column DDL while using , due to a lack of a referenced index. (MDEV-23387)
Server crash when altering a table after its tablespace has been discarded already. (MDEV-22939)
caused a variety of non-determinism failures if the given position did not exist. (MDEV-22473)
SET GLOBAL replicate_do_db = DEFAULT causes a crash. (MDEV-20744)
can crash if the first parameter is set to NULL and the second is not valid JSON. (MDEV-20593)
Server crashes after with ON DELETE SET NULL for a foreign key and a virtual column in the index. (MDEV-20396)
Server can crash on a prepared statement executed via MariaDB Connector/ODBC. (MDEV-19838)
Crash on on a table that contains indexed virtual columns. (MDEV-18366)
Possible server crash for queries using the window function (MDEV-15180)
got stuck after (MDEV-22707)
Server crash can occur when SET GLOBAL is used. (MDEV-23534)
Possible crash when using Tables and partitions. (MDEV-20100)
Optimizer has chosen an inefficient plan, if a multi-component index, a second index, and a WHERE or ON clause with conditions over these indexes are used. (MDEV-23811)
Some rounding has been done in an unexpected way for decimal numbers. (MDEV-23702)
Server crashes after changing at runtime via a statement. (MDEV-23693)
Creating a view removes parentheses on expressions from the , which results in wrong results. (MDEV-23656)
mysql_tzinfo_to_sql under is slow. (MDEV-23440)
UDF cannot be uninstalled if the UDF library file doesn't exist. (MDEV-23327)
with type can return an unexpected result if the given value for "expr" includes many leading zeros. (MDEV-23105)
replication is broken if only one timezone is loaded. (MDEV-22626)
SST donation fails, FLUSH TABLES WITH READ LOCK times out. (MDEV-22543)
Memory leaks possible after with FOREIGN KEY (MDEV-22277)
SST fails for if the data-directory has a lost+found directory. (MDEV-21951)
caused a variety of non-determinism failures if the given position did not exist. (MDEV-21839)
Linux AIO returned OS error 22 if parameters set to O_DIRECT and innodb_use_native_aio=1 (default). (MDEV-21584)
CREATE OR REPLACE TRIGGER in not replicating, if a trigger with the same name already exists. (MDEV-21578)
mysqld_multi no longer works with different server binaries. (MDEV-21526)
Possible error for incremental backup for encrypted tablespaces. (MDEV-20755)
Possible slow server starts and stops if full text indexes are used. (MDEV-18867)
The parentheses in a VIEW can be defined incorrectly for a combination of = and BETWEEN (MDEV-17408)
upon replaying the binary log. (MDEV-16372)
Several IPv6 issues with powered by Galera. (MDEV-21770, MDEV-23576, MDEV-23580, MDEV-23581, MDEV-23574)
Subquery on information_schema fails with error message. (MENT-1016)
AUTO_INCREMENT does not increment with a compound primary key on a partitioned table. (MENT-997)
CREATE TEMPORARY TABLE .. LIKE () returns an error if a unique index is defined in the table. (MDEV-23968)
CREATE .. SELECT can result in an empty result on a join versioned table. (MDEV-23799)
Error ERROR 4142 (HY000): SYSTEM_TIME partitions in table t1 do not support historical query upon querying a view, when that view is selecting from the versioned table with partitions. It only happens if the view itself was created using FOR SYSTEM_TIME ALL (MDEV-23779)
Disk Space not reused for Blob in the data file. (MDEV-23072)
will not dump sequence definition details on --no-data dump. (MDEV-21786)
fails to validate corruption on a table that was corrupted by a bug related to instant ADD or DROP (fixed in MariaDB Enterprise Server 10.3.17, 10.4.7). (MDEV-21251)
Subquery execution is not terminated after LIMIT ROWS EXAMINED is exceeded. (MDEV-18335)
Ubuntu 18.04
Ubuntu 20.04
Debian 9
Debian 10
SUSE Linux Enterprise Server 12
SUSE Linux Enterprise Server 15
Microsoft Windows
6.5
4.9
4.9
4.9
N/A (Critical)#1
MariaDB Enterprise Server 10.3.35-16 is a maintenance release of 10.3. This release includes a variety of fixes.
MariaDB Enterprise Server 10.3.35-16 was released on 2022-06-13.
CVE (with link)
CVSS base score
MariaDB Enterprise Server enables a predictable development and operations experience through an . These new features have been backported after reaching maturity in MariaDB Community Server:
reads data as of a specific timestamp from system-versioned tables. (MENT-1457)
Galera updated to 25.3.37
Spider storage engine refuses attempt to create a temporary table since the engine cannot itself store data and cannot create temporary tables on a remote server. ()
Status variables Innodb_encryption_key_rotation_list_length, Innodb_num_index_pages_written and Innodb_num_non_index_pages_written were unused and have been removed. (, )
Starting with this release, when is set to rsync
When the parser converts a string from the binary character set to a multi-byte character set (such as utf32), an invalid string could be produced. ()
When rows are inserted into an intermediate temporary table via the , and then the rows are copied from the temporary table to a persistent table, the rows are not written to the binary log if is set, which prevents the operation from properly replicating to replica servers. ()
When is set, can hang. ()
With MariaDB Enterprise Cluster, powered by Galera, when is set to rsync or mariadb-backup, the donor node does not transfer the correct binary logs to the joiner node with some configurations. ()
When a window function is used in the global ORDER BY clause of a with a UNION, the statement should be rejected, but the server executes the statement and crashes with a segmentation fault. ()
When a stored procedure queries a view and uses a for loop, the server can crash with a segmentation fault when the stored procedure is called twice in the same session. (
When is executed on a sequence, the server raises an , even if is set to ROW or MIXED. ()
The warning can appear in the MariaDB Error Log as follows:
When an or statement uses an OR clause, the server raises an . ()
The error can appear on the client as as follows:
When an uses a subquery inside an , the optimizer could incorrectly choose to perform a full table scan (with type: ALL) when a range scan (with type: range) would be more efficient. ()
When a table contains multiple columns with identical values, the values could become corrupt if multi-byte character sets are used. ()
When columns are read from , the server could incorrectly raise an warning. ()
With , the parser allows functions to be called using PACKAGE_NAME.FUNCTION_NAME(), but the parser raises an if the function is called using DATABASE_NAME.PACKAGE_NAME.FUNCTION_NAME(). ()
When a view is used to update multiple rows of a in a single , the server incorrectly raises an warning. ()
When using with and , events from the primary server's currently active log file are not written to their respective log file specified by --result-file. ()
When a prepared statement is used to execute , a different query plan can be returned on the second execution. ()
When is enabled with semi-synchronous replication, the numbering on packet headers can become out of sync between the primary and replica servers, but the inconsistency does not have any negative impact on release builds of MariaDB Enterprise Server. ()
This warning can be written to standard output (stdout) when preparing a backup with MariaDB Enterprise Backup.
This warning can be written to the MariaDB Error Log when InnoDB performs crash recovery at startup.
With MariaDB Enterprise Cluster, the joiner node fails to complete an SST when specifies a directory different than . ()
Galera snapshot transfer fails to upgrade between some major versions. ()
On Windows, the MSI installer does not install client shared libraries. ()
After upgrade, mysql.plugin table has an entry for Semi-sync Replication, though this former plugin functionality is now built in. ()
system variable removed
status variable removed
status variable removed
status variable removed
In alignment with the , MariaDB Enterprise Server 10.3.35-16 is provided for:
CentOS 7 (x86_64)
Debian 9 (x86_64, ARM64)
Debian 10 (x86_64, ARM64)
Microsoft Windows (x86_64)
Some components of MariaDB Enterprise Server might not support all platforms. For additional information, see "".
This is the final release for Debian 9.
This page is: Copyright © 2025 MariaDB. All rights reserved.
mariadb-backupsst_max_binlogssstThe default value is 0:
If a binlog exists, it will be transferred.
If a binlog does not exist, no binlog will be transferred.
Starting with this release, the has been removed.
When a replica server's I/O thread receives an incomplete event group from the primary server, the replica server continues writing events to the relay log and does not raise an error. (MDEV-27697)
Semisync-replica server recovery fails to rollback a prepared transaction. (MENT-1534)
Server can crash when a procedure that queries a view is called twice. (MDEV-26009)
When is executed on an encrypted tablespace file using the , innochecksum crashes with a segmentation fault unless the is also specified. (MDEV-27835)
When an invalid is used inside of a CREATE PROCEDURE or CREATE FUNCTION statement, the server can crash while parsing the statement. (MDEV-28220)
Possible crash on parsing a syntax incorrectly stated statement CREATE SEQUENCE .. RESTART inside of a ``CREATE PROCEDURE or CREATE FUNCTION` (MDEV-28220)
When a table contains a virtual generated column that is defined using the IF() and DATE_FORMAT() functions, inserting a row into the table can cause the server to crash with a segmentation fault. (MDEV-24176)
Server crash after INSERT in a table with a virtual column generated using date_format() and if() (MDEV-24176)
When a non-updatable view is defined with ALGORITHM=TEMPTABLE, selecting data from the view can cause the server to crash with a segmentation fault. (MDEV-21028)
When a UNION of decimal types is performed in an ORDER BY clause, the server can crash with a segmentation fault. (MDEV-25994)
When a stored procedure executes a query that results in a mergeable derived table, the server can crash with a segmentation fault when the stored procedure is called twice in the same session. (MDEV-27212)
Querying views can result in mergeable derived tables.
Using subqueries with outer references can result in mergeable derived tables.
When is executed with a query that contains a subquery, the server can crash. (MDEV-28268)
When a query using a window function with an OVER (PARTITION BY ..) or OVER (ORDER BY ..) clause is executed, the server can crash with a segmentation fault. (MDEV-19398)
If the query also uses WITH ROLLUP, this crash is more likely.
If the query's OVER (PARTITION BY ..) or OVER (ORDER BY ..) clause uses an aggregate function, this crash is more likely.
When a query contains an outer join expression and a non-correlated subquery that the optimizer determines is low cost, executing the query can cause the server to crash if the optimizer also determines that the inner join expression can be eliminated. (MDEV-28437)
With MariaDB Enterprise Cluster, a joiner node's binary logs could be deleted during an Incremental State Transfer (IST), which causes the node to fail to start, because it cannot read the binary logs. (MDEV-28583)
This issue is confirmed to happen with wsrep_sst_method set to rsync, but it might also occur with other SST/IST methods.
ALTER TABLE on a large InnoDB table can hang. (MDEV-28415)
The warning can appear on the client as follows after executing SHOW WARNINGS:
The warning can appear on the client as follows after executing :
The server and can raise unnecessary warnings about tablespace IDs in some scenarios. (MDEV-27343)
The warning can appear as follows:
DATA DIRECTORY clause is converted to a partitioned table, the DATA DIRECTORY clause is silently ignored, and the partitioned table is moved to the default directory. (MDEV-27065)Starting with this release, the server will raise the warning.
When a table contains an invisible column, does not produce the correct in the backup file. (MDEV-28253)
When a Spider table is queried using IF(COUNT() ..), the server can raise an . (MDEV-25116)
With MariaDB Enterprise Cluster, State Snapshot Transfers (SSTs) can fail on the donor node when binary logs are enabled. (MDEV-26201)
With MariaDB Enterprise Cluster, when wsrep_node_address contains an IPv6 address and wsrep_sst_receive_address is set to the default value of AUTO, State Snapshot Transfers (SST) can fail. (MDEV-26171)
With , replication can break if a system versioned table has been created on the replica via mariadb-dump, if the original table was altered before. (MDEV-28254)
mariadb-backup does not detect multi-source replication primary. (MDEV-21037)
Master_SSL_Crl shows Master_SSL_CA value in SHOW SLAVE STATUS output. (MDEV-28428)
MariaDB Audit plugin produces corrupted log entries for CONNECT events. (MENT-1438)
mariadb-dump does not create a dump where the sql_mode is set correctly for SQL/PL packages. (MDEV-27816)
Missing binlog data for INSERT .. ON DUPLICATE KEY UPDATE (MDEV-28310)
mariadb-backup prepare fails for incremental backups if a new schema is created after a full backup. (MDEV-28446)
Optimizer uses all partitions during an UPDATE and ignores partitioning filters. (MDEV-28246)
When is executed and is set to MIXED, the server raises an [e1592|[ER_BINLOG_UNSAFE_STATEMENT warning]] even though the statement is written to the binary log in row-based format. (MDEV-21810)
The warning can appear in the MariaDB Error Log as follows: <<sql inline=false>> [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. INSERT... ON DUPLICATE KEY UPDATE on a table with more than one UNIQUE KEY is unsafe Statement: INSERT INTO TABLE_NAME VALUES (..) ON DUPLICATE KEY UPDATE KEY_NAME = KEY_VALUE <<sql>>
When INSERT .. ON DUPLICATE KEY UPDATE is executed, and binlog_row_image is set to FULL, the server does not write unchanged columns to the binary log. (MDEV-21810)
Crash recovery fails if the configured server ID does not match the server ID in the crashed data directory. (MENT-1535)
mariadb-backup command-line option added
mysqldump command-line option added
Red Hat Enterprise Linux 8 (x86_64, ARM64)
Rocky Linux 8 (x86_64, ARM64)
SUSE Linux Enterprise Server 12 (x86_64)
SUSE Linux Enterprise Server 15 (x86_64, ARM64)
Ubuntu 18.04 (x86_64, ARM64)
Ubuntu 20.04 (x86_64, ARM64)
7.5
7.5
7.5
7.5
7.5
7.5
7.5
7.5
7.5
7.5
7.5
7.5
7.5
7.5
7.5
7.5
7.5
6.5
6.5
6.5
6.5
6.5
4.9
[Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement is unsafe because it uses a system function that may return a different value on the slave Statement: OPTIMIZE TABLE SEQUENCE_NAMEYou are using safe update mode, and you tried to update a table without a WHERE clause that uses a KEY columnEncountered illegal value '' when converting to DECIMALView being updated does not have the complete key of the underlying table in itInnoDB: Allocated tablespace ID TABLESPACE_ID for DATABASE_NAME/TABLE_NAME, old maximum was 04.9
New function calculates the spherical distance between two geometries (point or multipoint) on a sphere. (MDEV-13467)
Galera updated to 25.3.3
Issue deprecation warnings for values none, innodb, strict_none, strict_innodb (MDEV-25106)
fails to rename a column in an table and causes the server to crash. The table is not accessible after a restart. (MDEV-24763)
Table corruption or after on table with foreign key. (MDEV-24532)
deletes the current source file after a No space left on device error, before exiting. Only the incomplete target file is still available. (MDEV-25221)
Possible corruption in online for with ()
may delete current data on the . ()
Possible hang when or is used with and a multi-master setup. (MDEV-18874)
Possible memory corruption with MariaDB Enterprise Cluster when inserting values bigger than 4096 bytes into variable-length fields (, , , and related types). (MDEV-24978)
fails on compressed tables. (MDEV-25121)
Server crashes in check_grant upon invoking the function with enabled. ()
crashes when ) is set and is undefined. ()
Possible Server crash when . Only seen when using a table space per table, and if the tablespace size is increased at the time of the drop. ()
Possible server hang with InnoDB and indexed virtual columns after an error with , , or on virtual columns. ()
conflict resolution issues. ()
Index count mismatch due to aborted FULLTEXT INDEX ()
node crashes when inserting a row into a table that contains a virtual column and does not have a primary key. ()
Server crashes when InnoDB fails to add a new index on a new virtual column and a concurrent connection executes a query that accesses the freed virtual column. ()
subquery with correlation in the ON expression crashes. ()
Server crashes in row_undo_mod_clust_low upon rollback of read-only transaction. ()
Server crashes on the second execution of a stored procedure when the stored procedure uses an invalid multi-table statement to update a view. ()
startup hangs when a recovered transaction exists for the system tables and a DDL transaction need to be rolled back. ()
Server crashes when tries to fetch data from a table containing a FULLTEXT INDEX, and the table's tablespace was discarded. ()
Server crashes on when a WHERE condition references a derived table. ()
Potential hang in purge when virtual indexed columns exist. (MENT-1203)
After or , change buffer entries for secondary indexes are lost on restart. (MENT-1217)
Crashes with nested table value constructors. ()
Server crashes when an aggregate function is called on a table value constructed with the or functions. ()
Server crashes when a statement has a subquery that references a table value constructed with the or functions. ()
Server crashes when a statement has an IN() clause that references the UNION of two table values constructed with the or functions. ()
Possible memory corruption or crash if a table definition is evicted from the cache during a transaction commit. (MDEV-24811)
Server crashes when the function is called on a column. (MDEV-22703, MDEV-24958, MDEV-24942)
Server crashes when a statement queries an table and uses a JOIN (MDEV-24929)
Server crashes in optimize_schema_tables_memory_usage after from (MDEV-24868)
Server crashes when a FULLTEXT INDEX is added to an table, and the tablespace for the table was previously discarded. ()
Server crashes when the optimizer incorrectly removes a GROUP BY from a subquery, because the column is specified in both the list and the GROUP BY list. ()
Server crashes when a statement has a subquery in the FROM clause that contains a GROUP BY clause, and multiple indexes are used: one index is used to resolve the GROUP BY clause, and another index is used for the LATERAL DERIVED optimization. ()
conflict resolution issues. ()
SUM column from a derived table returns invalid values. (MDEV-23291)
returns an incorrect result. (MDEV-24790)
Incorrect behavior of when it is executed as a prepared statement. (MDEV-24860)
Query returns an when a subquery contains a JOIN with an ON clause that references an outer column. ()
Query returns an when a Common Table Expression (CTE) contains a UNION ()
Query returns wrong result when the or aggregate functions are used, and the aggregated column is indexed. ()
Wrong result (extra rows and wrong values) with incremental block nested loop hash. ()
Query returns wrong results when a JOIN is evaluated using the Block Nested Loop Hash (BLNH) optimization with a compound index. ()
Server fails to start using mysqld_multi with mysqld_safe options. ()
Duplicate key may be generated during a configuration change. ()
State snapshot transfer (SST) for using fails when the --log-bin option was set on the command-line with no value at server startup. ()
Race condition between persistent statistics and or ()
Race condition between and STATS_AUTO_RECALC ()
Incorrect message about field length is written to the error log when is executed on an table. ()
No error is returned when the optimizer removes a redundant part of a subquery that contains an unknown table alias. For example, if the optimizer removes a redundant GROUP BY clause from an subquery, unknown table aliases in the redundant part are ignored. ()
shown with in the field "filter" is incorrect for columns. ()
Histogram statistics are used even with ()
shows nonsensical value for key_len with type=index ()
SSL connection fails when server and client certs are signed by the same CA. ()
Wrong function name in error messages upon call. ()
fails on large backup. ()
State snapshot transfer (SST) for using fails when the password for the backup user is set via the MYSQL_PWD environment variable. ()
State snapshot transfer (SST) for using fails when the option was set on the command-line at server startup. ()
An extra warning is returned when the statement is executed in a prepared statement. ()
Complex query in stored procedure returns wrong results. ()
wrongly checks for the field's default value if AFTER is used. ()
Incorrect name resolution for subqueries in ON expressions. ()
When is executed, a race condition between group commit and binary log rotation causes the old binary log file to become obsolete before the group commit has been written to it. ()
MariaDB Enterprise Backup logs an error instead of a warning when it reads an invalid log block checksum during a --backup. ()
Rows are wrongly omitted when an InnoDB index is read using Multiversion Concurrency Control (MVCC). ()
aborts after failed into a table with a virtual column. ()
fails to fetch the index type when an index mismatch happens. ()
silently enables InnoDB Monitor output and never disables it when a wsrep slave thread tries to perform a brute-force (BF) kill, but fails due to a long lock wait. ()
RENAME TABLE causes "Ignoring data file ... with space ID xxxx, since the redo log references ... with space ID xxxx." for . ()
The Replication Heartbeat binary log event (Heartbeat_log_event) uses 4 bytes to store the log position within the current binary log file, so the log position overflows when the binary log file size exceeds 4 GB. ()
spatial indexes miss large geometry fields. (MENT-1205)
Table alias from previous statement interferes with later commands. (MENT-1200)
fails to replicate the statement when is enabled. ()
statement does not show details about sub-queries when the primary table is a table value constructed with the or functions. ()
JOIN of a materialized derived table returns the wrong result when the optimization is enabled. ()
Uninitialized value upon CREATE .. SELECT .. VALUE and a variety of resulting errors with different engines. ()
Dropping the primary key column from a always fails with Error 1072. ()
ALTER TABLE .. ADD COLUMN .. AS ROW START returns misleading error. ()
Unexpected error when the Primary Key column is dropped from a . ()
doesn't work properly with semi-sync replication. ()
Sequence created by one connection remains invisible to another. ()
routine_definition in loses tablename if it starts with an _ and is not backticked. ()
JOIN of a derived table using an aggregation function returns incorrect results. (MENT-1210)
/ not logged with MariaDB Audit Plugin. ()
Missing libsepol dependency on SLES 12 and SLES 15. (MENT-1163)
caching_sha2_password.so isn't included in Debian packages. (MDEV-24728)
Minor version upgrade does not perform a server restart. (MDEV-25240)
Interface Changes
command-line option added
skip-check-installed command-line option added
function added
In alignment with the enterprise lifecycle, MariaDB Enterprise Server 10.3.29-12 is provided for:
CentOS 7
CentOS 8
Debian 9
Debian 10
Red Hat Enterprise Linux 7
Red Hat Enterprise Linux 8
SUSE Linux Enterprise Server 12
SUSE Linux Enterprise Server 15
Ubuntu 18.04
Ubuntu 20.04
Microsoft Windows
Some components of MariaDB Enterprise Server might not support all platforms. For additional information, see "MariaDB Corporation Engineering Policies".
This page is: Copyright © 2025 MariaDB. All rights reserved.
CVE (with cve.org link)
CVSS base score
4.9
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.