CVEvulnerability

CVE-2026-119281

5.9 MEDIUM EPSS 0.28% Published 2026-10-29 Modified 2026-10-30 Official page ↗

Exploitation and prioritisation

EPSS
0.28% chance of exploitation in the next 30 days · in the top 79.1% of all CVEs (2026-11-03)
EU Vulnerability Database
EUVD-2026-113388

Affected packages

EcosystemPackageVulnerableFixed inAdvisory
Mavenorg.mariadb.jdbc:mariadb-java-client>= 3.0.0, < 3.3.73.3.7GHSA-grfq-r75j-rw9x
Mavenorg.mariadb.jdbc:mariadb-java-client>= 3.4.0, < 3.4.53.4.5GHSA-grfq-r75j-rw9x
Mavenorg.mariadb.jdbc:mariadb-java-client>= 3.5.0, < 3.5.113.5.11GHSA-grfq-r75j-rw9x
Status
Awaiting Analysis
Published
2026-10-29
Last modified
2026-10-30
Assigner
[email protected]
CVSS 3.1 ([email protected])
5.9 MEDIUM — CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
Weaknesses
CWE-838

Description

MariaDB Connector/J is used to connect applications developed in Java to MariaDB and MySQL databases. From 3.0.0 until 3.3.7, 3.4.5, and 3.5.11, the connector assumed result bytes were UTF-8 but guarded only changes to character_set_client. It did not reject non-UTF-8 character_set_results changes and relied on the server's global session_track_system_variables configuration to report character-set changes. A malicious or compromised server, or a machine-in-the-middle attacker, could suppress tracking or change the result charset so application strings differed from the returned bytes, potentially defeating application-side validation or escaping that depended on the decoded values. This issue is fixed in versions 3.3.7, 3.4.5, and 3.5.11.

Related

Weakness · CWE (1)

  • CWE-838 Inappropriate Encoding for Output Context weakness

Referenced by GitHub Advisory · alias (1)

  • GHSA-grfq-r75j-rw9x MariaDB Connector/J: Server could switch character_set_results away from UTF-8 without the client noticing advisory · Maven

References