Release 25.10.3 is a GA release.

Release Date: 15 Jun 2026

This document describes the changes in release 25.10.3, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read the for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on our Jira.

New Packages

Although a maintenance release, MaxScale 25.10.3 introduces some significant new functionality that, in order to not change the dependencies of exiting packages, are delivered in packages of their own.

maxscale-exasol

Contains , a MaxScale router that is capable of routing requests to an Exasol Analytics Engine.

maxscale-maxctrl2

Contains a reimplemenation of maxctrl. The primary differences to maxctrl are

• implemented in C++, so there is no dependency on node.js anymore, and

• provides TAB-completion, which makes interactive use significantly simpler.

Otherwise it is intended to be functionally equivalent with maxctrl.

• tabular output in ASCII (in 25.10.3-2, concerns maxscale-maxctrl2)

• show the table headers if --tsv is used (in 25.10.3-2, concerns maxscale-maxctrl2)

• Support of prepared statements in the diff router

• mxq::ODCB::disconnect() disconnects/frees handles in the wrong order (in 25.10.3-2, relevant for maxscale-exasol)

• X-HTTP-Method-Override header allows a basic user to perform admin operations

• Sysbench test fails vs exasol router (in 25.10.3-2, concerns maxscale-exasol)

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the document.

RPM and Debian packages are provided for the supported Linux distributions.

Packages can be downloaded .

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

• The diagnostic output of maxctrl show filter now shows the rules of a filter, if it has such.

• At startup, if there are filters that are not used by any service, or servers that are not referred to by any service or monitor, a warning will be logged.

• net_write_timeout now also affects backend connections.

• The global settings query_retry and query_retry_timeout, as well as the monitor settings backend_write_timeout and backend_read_timeout have been removed. The settings are still recognized but any configured values are ignored.

• The monitor setting backend_connect_timeout has been deprecated. Use backend_timeout instead.

• Now possible to clear service and server statistics using maxctrl.

• Support for compression protocols has been added to MaxScale. Both the traditional zlib compression as well as the newer zstd based compression protocols are supported by MaxScale.

• MaxGUI Query Editor now disables logging for auto-generated queries by default, while queries manually written and executed in the Query Editor are still logged. Logging for both types can now be managed in the General tab of the Preferences dialog.

• MaxScale now uses Forward-confirmed reverse DNS whenever resolving client IP addresses to hostnames. This is similar to how MariaDB handles reverse DNS lookups. The debug=disable-fcrdns debug option can be used to disable it in cases where there are issues with DNS servers.

• In the output of maxctrl list server, the state of a server and reason for the state are now separated. The state of a server is shown as Read, Write, Up or Down, possibly augmented with Maintenance or Draining|Drained, while the reason for the state is shown in the next column.

• Added simple syntax for maxctrl call command that allows object instances to be used in place of the module name. For example, the maxctrl call command mariadbmon switchover MariaDB-Monitor and maxctrl call command MariaDB-Monitor switchover are now both valid.

• Simple filters that have no settings are now automatically created by MaxScale whenever a service refers to them by the module name. For example, filters=hintfilter will enable routing hints for a service without having to define a separate filter section in the configuration.

• The statistics in readwritesplit and readconnroute that track session activity per backend have been replaced with a generic metric in the service that already tracked the average and maximum duration of a session. The max_session_active_pct and avg_session_active_pct track the maximum and average percentage that a session has been active, that is, when a query has been in execution on a backend server. This can also be thought of as the length of the session with the idle subtracted from it. The max_session_queries and avg_session_queries track the maximum and average number of queries an individual session has done.

• MaxScale can now send metrics to an OpenTelemetry Collector.

• Added command to MariaDB Monitor.

• Added discover-replicas command to both and .

• Added bootstrap command to both and .

• Added command to MariaDB Monitor.

• MariaDB Monitor (rebuild-server, create-backup, restore-from-backup) now support key-value arguments. The commands also support the dry-run-option, which checks if MaxScale configuration and servers support the commands.

• MariaDB Monitor backup operation status can be shown in detail with the command.

• Available backups can be listed with the MariaDB Monitor list-backups command.

• Added setting to MariaDB Monitor.

• Added to MariaDB Monitor.

• Added role support to monitors and services. See and settings for more information.

• MaxCtrl now attempts to read the [maxctrl] section from /etc/maxscale.cnf if the configuration file is present and readable. This can be used to customize the MaxCtrl options at a global level for all users.

• The maxctrl create server command has a new --copy option that uses the configuration of an existing server as the default configuration. This makes creating multiple similarly configured servers easier. For example, maxctrl create server server2 --copy server1 address=server2.my.host.com would use the settings of server1 for server2 but use a custom value for the address setting.

• Galera Monitor now requires the REPLICA MONITOR privilege and will fail to monitor the servers if lacking it. With MariaDB Server versions older than 10.5, REPLICATION CLIENT is required.

• It is now possible to dump the content of the query classifier cache using maxctrl.

• Listeners and servers support zero-configuration SSL, as described . See for more information.

• Added global setting which forces encryption to be configured everywhere.

• By default, MaxScale no longer generates a core file in case of a crash.

• The for redirect_url is intercepted and renamed by MaxScale to mxs_rdir_url. This is done to prevent accidental redirections away from MaxScale.

• The new parameter can be used to implement in MaxScale.

• session_trace_match is now matched for every logged message.

• When MaxScale is used with MariaDB 12 or later and the service user has the SET USER grant, the backend connections now log in using the service user credentials and then switch to the client user account using the new SET SESSION AUTHORIZATION feature in MariaDB 12. This makes it possible to use authentication plugins like ed25519 and PARSEC without having to configure anything extra in MaxScale. For more information, refer to the documentation of the setting.

• Added support for the PARSEC authentication plugin. The plugin can be used with MariaDB 12 directly and with MariaDB 11.6 or later if the user mapping file is used. For more information, refer to the authenticator documentation.

For more details, please refer to:

The changelog for the previous MaxScale version can be found .

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

Release 23.08.13 is a GA release.

Release Date: 16 Mar 2026

This document describes the changes in release 23.08.13, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read the for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on our Jira.

Bug fixes

• MXS-6212 Kafkacdc doesn't log GTID positions when losing ownership of a cluster

• maxctrl create report may truncate output

• kafkacdc doesn't enable TLS for replication connections

• Crash on malformed OK packet

• MaxScale uses a hard-coded value of LimitNOFILE=65535 in the systemd service file

• maxctrl alter user fails to process purely numeric passwords, resulting in "No password provided" error

• Table name parsing doesn't remove identifier quotes

• MaxScale WebUI: prevent load Adobe CSS for Internet-restricted sites

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the document.

RPM and Debian packages are provided for the supported Linux distributions.

Packages can be downloaded .

Release Date: 9 Jan 2026

Release 25.10.1 is a GA release.

This document describes the changes in release 25.10.1, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read the for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on our Jira.

External CVEs resolved.

• Fixed by Bump gui dependencies to fix vulnerabilities

• Fixed by Bump gui dependencies to fix vulnerabilities

• Fixed by Bump gui dependencies to fix vulnerabilities

• Support Okta SSO in maxscale

• Create an ExasolRouter

• give maxctrl its own installation package

• MaxScale WebUI: prevent load Adobe CSS for Internet-restricted sites

• No error message if connection to server fails during start of switchover

• SmartRouter should never return anything but resultsets from non-master targets

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the document.

RPM and Debian packages are provided for the supported Linux distributions.

Packages can be downloaded .

The source code of MaxScale is tagged at GitHub with a tag, which is identical with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale is maxscale-X.Y.Z. Further, the default branch is always the latest GA version of MaxScale.

The source code is available .

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

Release 25.01.5 is a GA release.

This document describes the changes in release 25.01.5, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read the for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on .

• No error message if connection to server fails during start of switchover

Release 24.02.9 is a GA release.

Release Date: 16 Mar 2026

This document describes the changes in release 24.02.9, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read the for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on .

• Kafkacdc doesn't log GTID positions when losing ownership of a cluster

This document describes the changes in release 23.08.3, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read the for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on .

• Crash on maxctrl list sessions

This document describes the changes in release 23.02.7, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read the for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on .

• Startup option --basedir mishandled

This document describes the changes in release 23.02.6, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read the for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on .

• Crash on maxctrl list sessions

This document describes the changes in release 23.02.8, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read the for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on .

• ssl_version should specify minimum version

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the document.

Release 25.10.2 is a GA release.

Release Date: 18 Mar 2026

This document describes the changes in release 25.10.2, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read the for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on our Jira.

New Features

• MXS-6085 Add support for MariaDB Advanced Cluster (RAFT) to Galera Monitor

Bug fixes

• Kafkacdc doesn't log GTID positions when losing ownership of a cluster

• maxctrl create report may truncate output

• maxctrl deprecation warning with nodejs 24.x and later

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the document.

RPM and Debian packages are provided for the supported Linux distributions.

Packages can be downloaded .

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

Release 25.01.7 is a GA release.

Release Date: 15 Jun 2026

This document describes the changes in release 25.01.7, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read the for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on our Jira.

Bug fixes

• MXS-6579 X-HTTP-Method-Override header allows a basic user to perform admin operations

• lower_case_table_names breaks kafkacdc replication

• trace_file_dir creates directory with inadequate permissions

• Connection unexpectedly closed if server dies after a transaction

• Configuration synchronization performance regression

• COM_RESET_CONNECTION doesn't clear out session command history

• Cooperative monitoring can lose exclusive locks if a server is slow to respond

• causal_reads=universal uses only the first GTID domain from the GTID list

• Using a shared storage with threading model thread_specific causes crash

• ssl operations fail from certain apps

• MariaDB Monitor does not properly verify its configuration when performing runtime modifications

• session_trace is always set to 1 if enabled

• MaxScale fails to start on upgrade if deprecated options are in the db config table.

• event_authentication_failure_level=LOG_EMERG does not produce log output on auth failure

• REST-API shouid send the Strict-Transport-Security header if HTTPS is used

• Missing Content-Type header for authentication failure responses

• MaxScale Crash (Signal 6) in Replicator during Partition DDL (Truncate/Add Partition)

• No header printed for log_data=command

• maxvisualize with empty queries array results in errors

• maxctrl call command executed for Reset-Replication we are seeing timeout error, But operation is successful.

• Cluster config sync - dont sync active/passive

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the document.

RPM and Debian packages are provided for the supported Linux distributions.

Packages can be downloaded .

This document describes the changes in release 24.02.6, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read the upgrading document for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on our Jira.

Bug fixes

• MXS-5618 Maxctrl interactive mode doesn't use --tls-verify-server-cert=false

• The logout screen is shown when accessing the MaxGUI login view.

• optimistic_trx causes a query to hang

• Processing of conditional headers is incorrect

• MaxCtrl fails to read large inputs from stdin

• admin_oidc_url is documented to not be dynamic when in fact it is

• REST-API always sends a Connection: close header

• Signal 11 crash when enabling causal reads with Galera

• Add a Service with a CLUSTER as its target breaks CONFIG SYNC

• Aborted connection on backend mariadb with persistpool maxscale

• Maxctrl config permission check error message is misleading

• Wrong password in interactive mode is only seen after the first command

• --secretsdir has no default value

• Query Editor default connection type preference is changed unexpectedly

• Using PKCS#1 private key in the REST-API results in cryptic errors

• Trailing parts of large session command are not routed correctly

• Prepared statements fail through schemarouter for ColumnStore

• Masking with functions uses wrong rule settings

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the document.

RPM and Debian packages are provided for the supported Linux distributions.

Packages can be downloaded .

The source code of MaxScale is tagged at GitHub with a tag, which is identical with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale is maxscale-X.Y.Z. Further, the default branch is always the latest GA version of MaxScale.

The source code is available .

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

Release 25.01.6 is a GA release.

Release Date: 16 Mar 2026

This document describes the changes in release 25.01.6, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read the for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on our Jira.

Bug fixes

• MXS-6212 Kafkacdc doesn't log GTID positions when losing ownership of a cluster

• maxctrl create report may truncate output

• maxctrl deprecation warning with nodejs 24.x and later

• kafkacdc doesn't enable TLS for replication connections

• Crash on malformed OK packet

• JSON output in rest API is reporting true/false for auto_failover as string

• MaxScale uses a hard-coded value of LimitNOFILE=65535 in the systemd service file

• maxctrl alter user fails to process purely numeric passwords, resulting in "No password provided" error

• Table name parsing doesn't remove identifier quotes

• Syncing MaxScale ends up with different JSON configuration

• Maintenance and drain statuses aren't synced with galeramon

• MaxScale masking-service crashing after upgrade

• Write test success message should be an info message

• No error or warning when using an unreadable PAM config

• CDC/Avrorouter Fails to Recover from Error 1236 When gtid_start_pos=newest

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the document.

RPM and Debian packages are provided for the supported Linux distributions.

Packages can be downloaded .

Release 24.02.10 is a GA release.

Release Date: 15 Jun 2026

This document describes the changes in release 24.02.10, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read the for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on our Jira.

Bug fixes

• MXS-6579 X-HTTP-Method-Override header allows a basic user to perform admin operations

• lower_case_table_names breaks kafkacdc replication

• Connection unexpectedly closed if server dies after a transaction

• Configuration synchronization performance regression

• COM_RESET_CONNECTION doesn't clear out session command history

• causal_reads=universal uses only the first GTID domain from the GTID list

• Using a shared storage with threading model thread_specific causes crash

• ssl operations fail from certain apps

• MaxScale fails to start on upgrade if deprecated options are in the db config table.

• event_authentication_failure_level=LOG_EMERG does not produce log output on auth failure

• REST-API shouid send the Strict-Transport-Security header if HTTPS is used

• Missing Content-Type header for authentication failure responses

• MaxScale Crash (Signal 6) in Replicator during Partition DDL (Truncate/Add Partition)

• No header printed for log_data=command

• maxctrl call command executed for Reset-Replication we are seeing timeout error, But operation is successful.

• Cluster config sync - dont sync active/passive

• heap-buffer-overflow in Rpl::process_row_event_data when reading data from ODBC test suite

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the document.

RPM and Debian packages are provided for the supported Linux distributions.

Packages can be downloaded .

This document describes the changes in release 24.02.1, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read the upgrading document for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on our Jira.

External CVEs resolved.

• CVE-2023-1667 Fixed by MXS-5011 Upgrade libssh to 0.10.6

• Fixed by Upgrade libssh to 0.10.6

• Fixed by Upgrade libssh to 0.10.6

• Fixed by Upgrade libssh to 0.10.6

• Fixed by Upgrade libssh to 0.10.6

• Add disk_space_ok option to master_conditions and slave_conditions

• Setting a path argument to empty reads uninitialized memory

• REST-API TLS keys are not validated at runtime

• MaxScale should prevent incompatible TLS certificates from being configured

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the document.

RPM and Debian packages are provided for the supported Linux distributions.

Packages can be downloaded .

The source code of MaxScale is tagged at GitHub with a tag, which is identical with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale is maxscale-X.Y.Z. Further, the default branch is always the latest GA version of MaxScale.

The source code is available .

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

This document describes the changes in release 23.08.1, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read the upgrading document for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on our Jira.

External CVEs resolved.

• CVE-2023-27371 Fixed by MXS-4751 Update libmicrohttpd to version 0.9.76

New Features

• Visualize response_time_distribution

• Add option to run PAM authentication in a suid sanbox

• REST-API generates too many errors for some endpoints

• Automatically ignored tables are not documented for schemarouter

• log_throttling should be disabled if log_info is on

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the document.

RPM and Debian packages are provided for the supported Linux distributions.

Packages can be downloaded .

The source code of MaxScale is tagged at GitHub with a tag, which is identical with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale is maxscale-X.Y.Z. Further, the default branch is always the latest GA version of MaxScale.

The source code is available .

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

This document describes the changes in release 23.02.16, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read the for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on our Jira.

Bug fixes

• MXS-6013 SHOW CREATE TABLE doesn't detect if a temporary table is used

• Default users_refresh_interval causes repeated user account loading

• maxctrl create report --archive error reporting produces errors

• kafkacdc doesn't escape db name identifiers resulting in errors

• Database names with dashes are not properly escaped when disabling events

• Fix for MXS-5196 can break "maxctrl create report"

• MaxKeys usage message is obsolete

• Rebuild Replica fails when using MaxScale encrypted password for monitor user

• MariaDBMon should not solely depend on "STOP SLAVE" when doing failover/switchover

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the document.

RPM and Debian packages are provided for the supported Linux distributions.

Packages can be downloaded .

The source code of MaxScale is tagged at GitHub with a tag, which is identical with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale is maxscale-X.Y.Z. Further, the default branch is always the latest GA version of MaxScale.

The source code is available .

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

This document describes the changes in release 23.08.12, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read the for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on our Jira.

Bug fixes

• MXS-6031 No error message if connection to server fails during start of switchover

• SHOW CREATE TABLE doesn't detect if a temporary table is used

• Signal 11 crash

• Default users_refresh_interval causes repeated user account loading

• maxctrl create report --archive error reporting produces errors

• kafkacdc doesn't escape db name identifiers resulting in errors

• Database names with dashes are not properly escaped when disabling events

• Fix for MXS-5196 can break "maxctrl create report"

• MaxKeys usage message is obsolete

• Rebuild Replica fails when using MaxScale encrypted password for monitor user

• MariaDBMon should not solely depend on "STOP SLAVE" when doing failover/switchover

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the document.

RPM and Debian packages are provided for the supported Linux distributions.

Packages can be downloaded .

The source code of MaxScale is tagged at GitHub with a tag, which is identical with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale is maxscale-X.Y.Z. Further, the default branch is always the latest GA version of MaxScale.

The source code is available .

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

This document describes the changes in release 23.08.4, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read the upgrading document for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on our Jira.

New Features

• MXS-4862 SSL_VERSION should have a way to disallow deprecated versions

Bug fixes

• Startup option --basedir mishandled

• Parameter table isn't refreshed after update in the GUI

• GUI doesn't show and allow to edit connection_metadata after a listener is created

• maxscale 23.08.3 crash with dump_last_statements=on_close set

• GUI failed to create a monitor in a monitored server detail page

• While writing query GUI response very slow

• No space or separator between 2 routing targets in the services dashboard

• Columns with the same name break sorting, filtering, and grouping features in Query Editor

• Broken slave promoted to master when no other servers are available

• GUI workspace caching doesn't work accurately

• Laggy issues on result data table

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the document.

RPM and Debian packages are provided for the supported Linux distributions.

Packages can be downloaded .

The source code of MaxScale is tagged at GitHub with a tag, which is identical with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale is maxscale-X.Y.Z. Further, the default branch is always the latest GA version of MaxScale.

The source code is available .

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

Release 23.08.14 is a GA release.

Release Date: 15 Jun 2026

This document describes the changes in release 23.08.14, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read the for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on our Jira.

Bug fixes

• MXS-6579 X-HTTP-Method-Override header allows a basic user to perform admin operations

• lower_case_table_names breaks kafkacdc replication

• Connection unexpectedly closed if server dies after a transaction

• Configuration synchronization performance regression

• COM_RESET_CONNECTION doesn't clear out session command history

• causal_reads=universal uses only the first GTID domain from the GTID list

• ssl operations fail from certain apps

• MaxScale fails to start on upgrade if deprecated options are in the db config table.

• event_authentication_failure_level=LOG_EMERG does not produce log output on auth failure

• REST-API shouid send the Strict-Transport-Security header if HTTPS is used

• Missing Content-Type header for authentication failure responses

• MaxScale Crash (Signal 6) in Replicator during Partition DDL (Truncate/Add Partition)

• maxctrl call command executed for Reset-Replication we are seeing timeout error, But operation is successful.

• Cluster config sync - dont sync active/passive

• heap-buffer-overflow in Rpl::process_row_event_data when reading data from ODBC test suite

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the document.

RPM and Debian packages are provided for the supported Linux distributions.

Packages can be downloaded .

Release 23.02.17 is a GA release.

Release Date: 16 Mar 2026

This document describes the changes in release 23.02.17, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read the for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on our Jira.

Bug fixes

• MXS-6212 Kafkacdc doesn't log GTID positions when losing ownership of a cluster

• maxctrl create report may truncate output

• kafkacdc doesn't enable TLS for replication connections

• Crash on malformed OK packet

• MaxScale uses a hard-coded value of LimitNOFILE=65535 in the systemd service file

• maxctrl alter user fails to process purely numeric passwords, resulting in "No password provided" error

• Table name parsing doesn't remove identifier quotes

• MaxScale WebUI: prevent load Adobe CSS for Internet-restricted sites

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the document.

RPM and Debian packages are provided for the supported Linux distributions.

Packages can be downloaded .

This document describes the changes in release 22.08.19, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read the for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on our Jira.

Bug fixes

• MXS-6013 SHOW CREATE TABLE doesn't detect if a temporary table is used

• Default users_refresh_interval causes repeated user account loading

• maxctrl create report --archive error reporting produces errors

• kafkacdc doesn't escape db name identifiers resulting in errors

• Database names with dashes are not properly escaped when disabling events

• Fix for MXS-5196 can break "maxctrl create report"

• MaxKeys usage message is obsolete

• Rebuild Replica fails when using MaxScale encrypted password for monitor user

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the document.

RPM and Debian packages are provided for the supported Linux distributions.

Packages can be downloaded .

The source code of MaxScale is tagged at GitHub with a tag, which is identical with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale is maxscale-X.Y.Z. Further, the default branch is always the latest GA version of MaxScale.

The source code is available .

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

This document describes the changes in release 23.02.1, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read the upgrading document for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on our Jira.

New Features

• MXS-4302 Implement a way to specify a list of users or exclude a list of users

• Add semi-sync support to Pinloki

• Dynamic filter capabilities do not work

• "Unknown prepared statement handler" error when connection_keepalive is disabled on a readconnroute service

• Empty regex // is not treated as empty

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the document.

RPM and Debian packages are provided for the supported Linux distributions.

Packages can be downloaded .

The source code of MaxScale is tagged at GitHub with a tag, which is identical with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale is maxscale-X.Y.Z. Further, the default branch is always the latest GA version of MaxScale.

The source code is available .

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

This document describes the changes in release 22.08.11, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read the upgrading document for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on our Jira.

Bug fixes

• MXS-4881 Startup option --basedir mishandled

• Parameter table isn't refreshed after update in the GUI

• GUI failed to create a monitor in a monitored server detail page

• No space or separator between 2 routing targets in the services dashboard

• Broken slave promoted to master when no other servers are available

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the document.

RPM and Debian packages are provided for the supported Linux distributions.

Packages can be downloaded .

The source code of MaxScale is tagged at GitHub with a tag, which is identical with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale is maxscale-X.Y.Z. Further, the default branch is always the latest GA version of MaxScale.

The source code is available .

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

This document describes the changes in release 22.08.10, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read the upgrading document for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on our Jira.

Bug fixes

• MXS-4847 Crash on maxctrl list sessions

• Binlog encryption broken

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the document.

RPM and Debian packages are provided for the supported Linux distributions.

Packages can be downloaded .

The source code of MaxScale is tagged at GitHub with a tag, which is identical with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale is maxscale-X.Y.Z. Further, the default branch is always the latest GA version of MaxScale.

The source code is available .

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

This document describes the changes in release 25.01.3, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please see .

For any problems you encounter, please consider submitting a bug report on .

• Network options for maxvisualize are not documented

This document describes the changes in release 24.02.7, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please see .

For any problems you encounter, please consider submitting a bug report on .

• Add MAXSCALE_USER and MAXSCALE_PASSWORD environment variables

This document describes the changes in release 24.02.3, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read the for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on .

• webpack warns about yargs

This document describes the changes in release 23.08.11, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please see .

For any problems you encounter, please consider submitting a bug report on .

• Add MAXSCALE_USER and MAXSCALE_PASSWORD environment variables

This document describes the changes in release 23.02.15, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please see .

For any problems you encounter, please consider submitting a bug report on .

• Add MAXSCALE_USER and MAXSCALE_PASSWORD environment variables

This document describes the changes in release 23.02.14, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read the for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on .

• Maxctrl interactive mode doesn't use --tls-verify-server-cert=false

This document describes the changes in release 23.02.2, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read the for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on .

• Query classifier does not classify XA transactions correctly.

This document describes the changes in release 23.08.10, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read the for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on .

• Maxctrl interactive mode doesn't use --tls-verify-server-cert=false

This document describes the changes in release 22.08.18, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please see .

For any problems you encounter, please consider submitting a bug report on .

• Add MAXSCALE_USER and MAXSCALE_PASSWORD environment variables

Release 23.02.18 is a GA release.

Release Date: 15 Jun 2026

This document describes the changes in release 23.02.18, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read the for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on .

• X-HTTP-Method-Override header allows a basic user to perform admin operations

This document describes the changes in release 21.06.20, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read the for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on .

• Maxctrl interactive mode doesn't use --tls-verify-server-cert=false

This document describes the changes in release 24.02.8, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read the for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on .

• No error message if connection to server fails during start of switchover

• The default values of some readwritesplit parameters have been updated. The new default values are:

  • master_reconnection=true

  • master_failure_mode=fail_on_write

  • strict_tmp_tables=true

  • transaction_replay_timeout=30s

• MariaDB-Monitor now requires MariaDB Server 10.4 or newer for failover/ switchover. Server 10.3 is end of life.

• Server setting private_address added. Used for detecting and setting up replication. See for more information.

• MariaDB-Monitor allows customization of some mariadb-backup settings. See and for more information.

• MariaDB-Monitor setting servers_no_promotion now affects primary server selection during MaxScale startup or due to replication topology changes.

• Pam authentication now always checks account status. Previously, this check was not performed if MaxScale was configured for username mapping (authenticator_options=pam_backend_mapping=mariadb). This means that if username mapping is configured in the OS pam service config, the final username must be a valid user. This is similar to MariaDB Server behavior.

• Support for the legacy SysV and Upstart system managers has been removed. In practice this change will not affect anything as all supported operating systems use SystemD as the system manager and MaxScale has long preferred it over the legacy systems.

• The output of maxctrl show service now includes the statistics for the services.

• The max_sescmd_history_length and avg_sescmd_history_length statistics in readwritesplit were moved into the core as service statistics. The session command history was moved into the MaxScale core in MaxScale 6 but the statistics were not updated to match this.

• Several redundant schemarouter statistics have been either replaced by statistics that are found in the general service statistics output or have been removed if they were irrelevant.

  • longest_sescmd_chain replaced by max_sescmd_history_length.

  • queries

• admin_readwrite_hosts and admin_readonly_hosts added. These settings limit the allowed source addresses for admin (REST-API) connections. See for more information.

• The alter commands in MaxCtrl now allow modifications to thetargets, servers, filters and cluster parameters for monitors and services. This makes it easier to define the exact set of servers that is to be used by a monitor or a service.

• The feature no longer requires modifying session_track_system_variables on the server. MaxScale adds last_gtid to the variable automatically for each session. Clients should not modify it manually.

• The now logs the execution of the binary protocol statements as text. This makes it so that for all execution of SQL, the query value in log_data will produce output.

• The functionality that the auth_all_servers parameter enabled is automatically enabled by the schemarouter whenever it is used.

For more details, please refer to:

The changelog for the previous MaxScale version can be found .

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

• The global setting skip_permission_checks has been deprecated and is ignored. Monitors start regardless of monitor user permissions.

• The uppercase versions of the slave_selection_criteria parameter in readwritesplit have been deprecated. All runtime modifications to the parameters are now saved using the lowercase versions.

• By default, readwritesplit will not replay transactions that are about to commit when transaction_replay is enabled. To retain the old behavior where transactions were always replayed, disable transaction_replay_safe_commit.

• Readwritesplit will now retry queries with partially returned results if they are done inside a transaction and transaction_replay is enabled.

• prune_sescmd_history now also performs history simplification by removing redundant executions of the same statement. This will reduce memory usage in the case when history repeats a small cycle of commands. One example of this is connection pools that prepare the connection with a small set of commands like SET NAMES and SET SQL_MODE.

• Common configuration settings can now be specified in a separate section, to be included by other sections.

• When changing the service password, the previous password will be retained and continue to be used if the new does not work.

• Embedded newlines are removed from logged messages.

• Schemarouter database map caches can be cleared with maxctrl call command schemarouter clear <service> where <service> is a service that uses the schemarouter.

• Schemarouter now allows stale cache entries to be used while the database map cache is being updated. By default the entries are usable for 150 seconds after they have gone stale. This limit can be configured with themax_staleness parameter.

• Added switchover-force command to MariaDB Monitor. This command performs a switchover even if primary server is unresponsive.

• Switchover now uses a longer command timeout on the old master. This should remove the need for adjusting monitor setting backend_read_timeout to get switchover to work.

• The NoSQL protocol now provides internal caching.

• Additional metadata is sent in the connection handshake. For more information, refer to the documentation.

• The connection_timeout parameter was renamed to wait_timeout to make the naming of the parameters the same in MaxScale and MariaDB server. The oldconnection_timeout parameter is now an alias to wait_timeout and its use has been deprecated. If used, a warning will be logged that the parameter is deprecated.

• The strip_db_esc parameter has been deprecated. The default behavior of stripping the escape characters is in all known cases the correct thing to do. Only broken legacy versions where the grants would be returned without backslash escaping would require this parameter to work.

• The Xpand monitor is now region aware.

• Passthrough authentication mode added to MariaDBAuth-module. See for more information.

• Added pam_mode=suid option to PamAuth module. This option separates the pam system library calls to a separate executable. See for more information. test_pam_login tool updated to support this mode.

• Added disk_space_ok option to MariaDB Monitor settings master_conditions and slave_conditions. Enabled by default in master_conditions. See for more information. Only available in MaxScale 23.08.5, 24.02.1 and later.

For more details, please refer to:

The changelog for the previous MaxScale version can be found .

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

This document describes the changes in release 23.08.6, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read the upgrading document for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on our Jira.

New Features

• MXS-5067 Add "enforce_read_only_servers" feature to MariaDB Monitor

Bug fixes

• Server version checks are overly pessimistic

• MariaDB Monitor can kill connections from other monitors during switchover

• Master Stickiness state is not documented

• Stacktraces fail to be generated when MaxScale is run from the terminal

• SQL API does not return binary data in resultsets

• admin_audit file name does not use log_dir value

• ability to setup .secrets file location

• max_slave_connections=0 may create slave connections after a switchover

• ssl_version in MaxScale and tls_version in MariaDB behave differently

• Password encryption format change in 2.5 is not documented very well

• The values of ssl_version in MaxScale and tls_version in MariaDB accept different values

• Warning about missing slashes around regular expressions is confusing

• users_refresh_time=0s does not work as documented

• Maxscale crash - "terminate called after throwing an instance of 'std::bad_alloc'"

• cmake does not check for unixodbc-dev

• Problem in hostname matching when using regex (%) for user authentication

• maxctrl alter admin_ssl_* not actually updating

• cooperative_monitoring_locks can leave stale locks on a server if network breaks

• Maxscale key limitations

• Setting a path argument to empty reads uninitialized memory

• REST-API TLS keys are not validated at runtime

• MaxScale should prevent incompatible TLS certificates from being configured

• enforce_read_only_slaves can set master to read_only

• kill user and transaction_replay don't play well together in Galera cluster

• gdb-stacktrace is incorrectly presented as a debug option

• Session commands that are executed early are not validated

• maxscale crash

• Simple sharding tutorial is out of date

• MariaDB Monitor command reset-replication can be started on a secondary MaxScale

• MaxScale should log a warning if failover may lose transactions

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the document.

RPM and Debian packages are provided for the supported Linux distributions.

Packages can be downloaded .