CVE-2026-119281 · GHSA-grfq-r75j-rw9x

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

Risk score: 40/100
CVSS: 5.9 v3.1
Published: 29 Oct 2026

Open in the live forecast Today's forecast

What to know

What it is: 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 se…
Affected: org.mariadb.jdbc:mariadb-java-client (maven) >= 3.0.0, < 3.3.7; org.mariadb.jdbc:mariadb-java-client (maven) >= 3.4.0, < 3.4.5; org.mariadb.jdbc:mariadb-java-client (maven) >= 3.5.0, < 3.5.11
Fix: Upgrade org.mariadb.jdbc:mariadb-java-client to 3.3.7 or 3.4.5 or 3.5.11 (whichever matches your release line) or later.
Exploitation: No known exploitation

Story map

Story map: the flaws, the fix, how it unfolded and what it connects to. Boxes link to the record or article.

At a glance

org.mariadb.jdbc:mariadb-java-client: Yellow, plan it in. 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 se…

The flaws

CVE-2026-119281: MariaDB Connector/J: Server could switch character_set_results away from UTF-8 without the client noticing (CVSS 5.9)
CVE-2026-119210: MariaDB Connector/J: LOAD DATA LOCAL INFILE file check could be satisfied by text inside quoted identifiers, letting a malicious server read client files (CVSS 5.9)
CVE-2026-119276: MariaDB Connector/J: Rogue server can drive large heap allocations from server-declared lengths in OK packets (CVSS 5.9)
CVE-2026-119279: MariaDB Connector/J: Length-encoded integers larger than Integer.MAX_VALUE were truncated before being used as lengths (CVSS 5.9)

The fix

Upgrade org.mariadb.jdbc:mariadb-java-client: 3.3.7 · 3.4.5 · 3.5.11 · 3.5.10 or later on your release line

Who is exposed: org.mariadb.jdbc:mariadb-java-client (maven) >= 3.0.0, < 3.3.7; org.mariadb.jdbc:mariadb-java-client (maven) >= 3.4.0, < 3.4.5; org.mariadb.jdbc:mariadb-java-client (maven) >= 3.5.0, < 3.5.11

Where it stands

No known exploitation

Connects to

Same weakness: CWE-838 (CWE-838). 1 other warning in 30 days

Why it is Yellow

CVSS 5.9 medium
On your watchlist: Maven

Affected packages

Package	Ecosystem	Vulnerable	Fixed in
org.mariadb.jdbc:mariadb-java-client	maven	>= 3.0.0, < 3.3.7	3.3.7
org.mariadb.jdbc:mariadb-java-client	maven	>= 3.4.0, < 3.4.5	3.4.5
org.mariadb.jdbc:mariadb-java-client	maven	>= 3.5.0, < 3.5.11	3.5.11

References

Original 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.

Last activity 30 Oct 2026. Patch Forecast updates every hour.