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

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 ClientMessage.validateLocalFileName() check used a regular expression that could match LOAD DATA LOCAL INFILE text inside quoted identifiers, string literals, or comments…
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 ClientMessage.validateLocalFileName() check used a regular expression that could match LOAD DATA LOCAL INFILE text inside quoted identifiers, string literals, or comments…

The flaws

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)
CVE-2026-119281: MariaDB Connector/J: Server could switch character_set_results away from UTF-8 without the client noticing (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-73 (CWE-73). 71 other warnings 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 ClientMessage.validateLocalFileName() check used a regular expression that could match LOAD DATA LOCAL INFILE text inside quoted identifiers, string literals, or comments instead of requiring a real statement. A malicious or compromised server, or a machine-in-the-middle attacker, could return crafted database or table identifiers that the connector reused in metadata or updatable-result queries, then answer with a LOCAL INFILE request for a client file. With allowLocalInfile enabled, this caused the connector to stream any readable client-host file named by the crafted text, including through DatabaseMetaData.getImportedKeys(), DatabaseMetaData.getExportedKeys(), or ResultSet.updateRow() paths. This issue is fixed in versions 3.3.7, 3.4.5, and 3.5.11.