> 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.10/25.10.4.md).

# MaxScale 25.10.4 Release Notes

Release 25.10.4 is a GA release.

**Release Date:** 17 Sep 2026

This document describes the changes in release 25.10.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](/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).

## New Features

* [MXS-6771](https://jira.mariadb.org/browse/MXS-6771) Query Cache | min\_query\_duration
* [MXS-6770](https://jira.mariadb.org/browse/MXS-6770) create a dedicate path variable to isolate where look for .maxctrl.cnf

## Bug fixes

* [MXS-6925](https://jira.mariadb.org/browse/MXS-6925) Readwritesplit closes session immediately if the current master server cannot be connected to
* [MXS-6922](https://jira.mariadb.org/browse/MXS-6922) \[maxctrl] section is not ignored on startup
* [MXS-6886](https://jira.mariadb.org/browse/MXS-6886) SQL\_MODE tracked by MaxScale is not reset on COM\_CHANGE\_USER/COM\_RESET\_CONNECTION
* [MXS-6880](https://jira.mariadb.org/browse/MXS-6880) MaxScale treats SET GLOBAL SQL\_MODE=ORACLE as if it was SET SESSION
* [MXS-6876](https://jira.mariadb.org/browse/MXS-6876) Server-specific settings monitoruser and monitorpw were not always used
* [MXS-6872](https://jira.mariadb.org/browse/MXS-6872) With NoSQL protocol, a malformed packet can cause MaxScale to crash
* [MXS-6868](https://jira.mariadb.org/browse/MXS-6868) exasol router | unclear error message when missing servers
* [MXS-6867](https://jira.mariadb.org/browse/MXS-6867) SET wait\_timeout is not respected by MaxScale
* [MXS-6864](https://jira.mariadb.org/browse/MXS-6864) Loss of master lock should trigger a hangup
* [MXS-6859](https://jira.mariadb.org/browse/MXS-6859) Certain types of network errors should trigger an immediate server DNS lookup
* [MXS-6844](https://jira.mariadb.org/browse/MXS-6844) Escape untrusted content before rendering as HTM
* [MXS-6842](https://jira.mariadb.org/browse/MXS-6842) maxctrl2: api get does not produce identical output
* [MXS-6841](https://jira.mariadb.org/browse/MXS-6841) Signed integer overflow with very large pagination values
* [MXS-6840](https://jira.mariadb.org/browse/MXS-6840) maxctrl2: When outputting TSV, whitespace should be folded into a space.
* [MXS-6839](https://jira.mariadb.org/browse/MXS-6839) maxctrl2: classify prints function names as a JSON array
* [MXS-6838](https://jira.mariadb.org/browse/MXS-6838) maxctrl2: Time is not printed as in the old maxctrl.
* [MXS-6837](https://jira.mariadb.org/browse/MXS-6837) maxctrl2: : 'show dbusers' formatting different from old maxctrl
* [MXS-6836](https://jira.mariadb.org/browse/MXS-6836) External Typekit stylesheet loaded without SRI
* [MXS-6825](https://jira.mariadb.org/browse/MXS-6825) maxctrl2: Connection errors are reported as "Unspecified HTTP error"
* [MXS-6819](https://jira.mariadb.org/browse/MXS-6819) A larger set of functions should cause the result of a SELECT not to be cached.
* [MXS-6810](https://jira.mariadb.org/browse/MXS-6810) Missing X-Content-Type-Options: nosniff
* [MXS-6774](https://jira.mariadb.org/browse/MXS-6774) Routing failure does not always send an error to the client
* [MXS-6759](https://jira.mariadb.org/browse/MXS-6759) maxctrl2: Wrong HTTP method (DEL instead of DELETE)
* [MXS-6756](https://jira.mariadb.org/browse/MXS-6756) maxctrl2: `list queries` doesn't report an error if retain\_last\_statement is disabled
* [MXS-6753](https://jira.mariadb.org/browse/MXS-6753) maxctrl2: `show commands` output is wrong
* [MXS-6752](https://jira.mariadb.org/browse/MXS-6752) maxctrl2: `list roles` formatting differs from old maxctrl
* [MXS-6751](https://jira.mariadb.org/browse/MXS-6751) maxctrl2: Output of `show threads` is not colorized
* [MXS-6750](https://jira.mariadb.org/browse/MXS-6750) maxctrl2: --help output uses absolute path to binary as program name
* [MXS-6745](https://jira.mariadb.org/browse/MXS-6745) maxctrl2: output of 'show qc\_cache' is not consistent with old maxctrl
* [MXS-6737](https://jira.mariadb.org/browse/MXS-6737) PAM Authentication Deadlock & Worker Thread Freeze
* [MXS-6736](https://jira.mariadb.org/browse/MXS-6736) Smartrouter regression in large payload handling
* [MXS-6735](https://jira.mariadb.org/browse/MXS-6735) SET commands with slow master response hits a debug assertion
* [MXS-6733](https://jira.mariadb.org/browse/MXS-6733) Interrupted measurement causes entry to never be updated
* [MXS-6726](https://jira.mariadb.org/browse/MXS-6726) MXS-5915 Still broken on MaxScale 24.02.9 with MariaDB 12.2/12.3 — TRUE/FALSE not handled
* [MXS-6725](https://jira.mariadb.org/browse/MXS-6725) max\_auth\_errors\_until\_block blocking complete hosts and causing outage
* [MXS-6705](https://jira.mariadb.org/browse/MXS-6705) Configuration synchronization unnecessarily destroys all objects
* [MXS-6704](https://jira.mariadb.org/browse/MXS-6704) Empty passwords in monitors and services do not work with configuration synchronization
* [MXS-6703](https://jira.mariadb.org/browse/MXS-6703) config\_sync\_password cannot be an empty string
* [MXS-6702](https://jira.mariadb.org/browse/MXS-6702) Crash if command byte is 0xFF
* [MXS-6700](https://jira.mariadb.org/browse/MXS-6700) Crash on KILL\tUSER\tfoobar
* [MXS-6671](https://jira.mariadb.org/browse/MXS-6671) Maxscale memory is increasing linearly over the period of a week
* [MXS-6616](https://jira.mariadb.org/browse/MXS-6616) maxctrl2 terminates if invoked in directory without write rights
* [MXS-6581](https://jira.mariadb.org/browse/MXS-6581) KafkaCDC causes segfault when processing geometry datatype events
* [MXS-6037](https://jira.mariadb.org/browse/MXS-6037) Smartrouter bug when servers go down
* [MXS-5924](https://jira.mariadb.org/browse/MXS-5924) MaxScale 24.02.6 automatic purging binlogs doesn't work and opens unlimited count of FD in OS Ubuntu

## 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).

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

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