NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · Maven

CVE-2026-119281: MariaDB Connector/J: Server could switch character_set_results away from UTF-8 without the client noticing

mediumCVSS 3.1 5.9GHSA-grfq-r75j-rw9x

Summary MariaDB Connector/J decodes every result as UTF-8 and guards charactersetclient against a change to another charset, but did not guard charactersetresults, and relied on the server's global sessiontracksystemvariables list to be told about charset changes at all.

Published Oct 30, 2026

Affected packages

org.mariadb.jdbc:mariadb-java-client

Ecosystem
Maven
Affected
>= 3.0.0, < 3.3.7
Fixed in
3.3.7
Check
mvn dependency:tree -Dincludes=org.mariadb.jdbc:mariadb-java-client

org.mariadb.jdbc:mariadb-java-client

Ecosystem
Maven
Affected
>= 3.4.0, < 3.4.5
Fixed in
3.4.5
Check
mvn dependency:tree -Dincludes=org.mariadb.jdbc:mariadb-java-client

org.mariadb.jdbc:mariadb-java-client

Ecosystem
Maven
Affected
>= 3.5.0, < 3.5.11
Fixed in
3.5.11
Check
mvn dependency:tree -Dincludes=org.mariadb.jdbc:mariadb-java-client

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

Summary

MariaDB Connector/J decodes every result as UTF-8 and guards character_set_client against a change to another charset, but did not guard character_set_results, and relied on the server's global session_track_system_variables list to be told about charset changes at all.

Details

The connector learns about session variable changes through session tracking, and closes the connection when character_set_client is switched away from UTF-8, so that its UTF-8 decoding stays correct. Two gaps remained:

  • character_set_results was not guarded: a server could switch it to another charset, after which the bytes of every result were decoded as UTF-8 although encoded otherwise.
  • the list of tracked variables came from the server's global session_track_system_variables: a server configured, or made, not to track the character set variables could change them silently.

The fix requests an explicit session tracking list that includes both character set variables whatever the server's global setting, and closes the connection when character_set_results is changed to a charset other than utf8, utf8mb3 or utf8mb4, as it already did for character_set_client.

Impact

Integrity: a malicious or compromised server, or a MitM, can make the strings an application reads differ from the bytes the server returned (inappropriate encoding for the output context), which can defeat application-side validation or escaping built on those values. Exploitation requires control of the server side of the connection; no confidentiality or availability impact.

Credit

Reported by fg0x0

Credited to fg0x0.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More Maven vulnerabilities

All Maven entries