> For the complete documentation index, see [llms.txt](https://mariadb.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mariadb.com/docs/release-notes/maxscale/25.01/25.01.7.md).

# MaxScale 25.01.7 Release Notes

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 [upgrading document](/docs/maxscale/maxscale-management/deployment/upgrading-maxscale.md) for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on [our Jira](https://jira.mariadb.org/projects/MXS).

## Bug fixes

* [MXS-6579](https://jira.mariadb.org/browse/MXS-6579) X-HTTP-Method-Override header allows a basic user to perform admin operations
* [MXS-6566](https://jira.mariadb.org/browse/MXS-6566) lower\_case\_table\_names breaks kafkacdc replication
* [MXS-6564](https://jira.mariadb.org/browse/MXS-6564) trace\_file\_dir creates directory with inadequate permissions
* [MXS-6563](https://jira.mariadb.org/browse/MXS-6563) Connection unexpectedly closed if server dies after a transaction
* [MXS-6536](https://jira.mariadb.org/browse/MXS-6536) Configuration synchronization performance regression
* [MXS-6508](https://jira.mariadb.org/browse/MXS-6508) COM\_RESET\_CONNECTION doesn't clear out session command history
* [MXS-6463](https://jira.mariadb.org/browse/MXS-6463) Cooperative monitoring can lose exclusive locks if a server is slow to respond
* [MXS-6461](https://jira.mariadb.org/browse/MXS-6461) causal\_reads=universal uses only the first GTID domain from the GTID list
* [MXS-6420](https://jira.mariadb.org/browse/MXS-6420) Using a shared storage with threading model thread\_specific causes crash
* [MXS-6381](https://jira.mariadb.org/browse/MXS-6381) ssl operations fail from certain apps
* [MXS-6374](https://jira.mariadb.org/browse/MXS-6374) MariaDB Monitor does not properly verify its configuration when performing runtime modifications
* [MXS-6367](https://jira.mariadb.org/browse/MXS-6367) session\_trace is always set to 1 if enabled
* [MXS-6366](https://jira.mariadb.org/browse/MXS-6366) MaxScale fails to start on upgrade if deprecated options are in the db config table.
* [MXS-6365](https://jira.mariadb.org/browse/MXS-6365) event\_authentication\_failure\_level=LOG\_EMERG does not produce log output on auth failure
* [MXS-6305](https://jira.mariadb.org/browse/MXS-6305) REST-API shouid send the Strict-Transport-Security header if HTTPS is used
* [MXS-6304](https://jira.mariadb.org/browse/MXS-6304) Missing Content-Type header for authentication failure responses
* [MXS-6283](https://jira.mariadb.org/browse/MXS-6283) MaxScale Crash (Signal 6) in Replicator during Partition DDL (Truncate/Add Partition)
* [MXS-6281](https://jira.mariadb.org/browse/MXS-6281) No header printed for log\_data=command
* [MXS-6280](https://jira.mariadb.org/browse/MXS-6280) maxvisualize with empty queries array results in errors
* [MXS-6265](https://jira.mariadb.org/browse/MXS-6265) maxctrl call command executed for Reset-Replication we are seeing timeout error, But operation is successful.
* [MXS-6238](https://jira.mariadb.org/browse/MXS-6238) Cluster config sync - dont sync active/passive

## Known Issues and Limitations

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the [Limitations](/docs/maxscale/maxscale-management/mariadb-maxscale-limitations-guide.md) document.

## Packaging

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

Packages can be downloaded [here](https://mariadb.com/downloads).