org.mariadb.jdbc:mariadb-java-client · MariaDB Connector/J: Server could switch character_set_results away from UTF-8 without the client noticing
Affects org.mariadb.jdbc:mariadb-java-clientSource GCVE Database
Not known to be exploited · CVSS 5.9 Medium : upgrade to 3.3.7 when convenient.
Data as of 31 Oct 2026, 02:06 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 5.9 |
|---|
- Patch
- Available – fixed in 3.3.7, 3.4.5, 3.5.11
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 29 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade org.mariadb.jdbc:mariadb-java-client to 3.3.7; org.mariadb.jdbc:mariadb-java-client to 3.4.5; org.mariadb.jdbc:mariadb-java-client to 3.5.11.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Mavenorg.mariadb.jdbc:mariadb-java-client | Affected
| Fixed in
|
| Mavenorg.mariadb.jdbc:mariadb-java-client | Affected
| Fixed in
|
| Mavenorg.mariadb.jdbc:mariadb-java-client | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in MariaDB Connector/J versions 3.3.7, 3.4.5, and 3.5.11. Users should upgrade to these or later versions to ensure the connector properly guards against changes to character_set_results and enforces correct session tracking. No additional mitigation is required beyond applying the official fix.
Description
MariaDB Connector/J versions 3.0.0 through before 3.3.7, 3.4.0 through before 3.4.5, and 3.5.0 through before 3.5.11 have a vulnerability where the connector does not properly guard against changes to the character_set_results session variable. This allows a malicious or compromised server to switch the character set away from UTF-8 without the client noticing, causing incorrect decoding of query results. This can lead to integrity issues where application-side validation or escaping based on string values can be bypassed. The vulnerability requires control of the server side of the connection and does not impact confidentiality or availability. Fixed versions are 3.3.7, 3.4.5, and 3.5.11.
References
- github.com/mariadb-corporation/mariadb-connector-j/security/advisories/GHSA-grfq-r75j-rw9x (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-119281 (opens in a new tab)
- github.com/mariadb-corporation/mariadb-connector-j/commit/af5e565eb171cfc66ea8e948ddc616abed0c4623 (opens in a new tab)
- github.com/mariadb-corporation/mariadb-connector-j/commit/d51b968c1b795c73d24e0b3f960205b7bc82d423 (opens in a new tab)
- github.com/mariadb-corporation/mariadb-connector-j/commit/fdabe74a7df6dce1d6c099f4d0ca1e2acc25919a (opens in a new tab)
- github.com/mariadb-corporation/mariadb-connector-j (opens in a new tab)
- github.com/mariadb-corporation/mariadb-connector-j/releases/tag/3.3.7 (opens in a new tab)
- github.com/mariadb-corporation/mariadb-connector-j/releases/tag/3.4.5 (opens in a new tab)
- github.com/mariadb-corporation/mariadb-connector-j/releases/tag/3.5.11 (opens in a new tab)