CVE-2026-119210 json
MariaDB Connector/J: LOAD DATA LOCAL INFILE file check could be satisfied by text inside quoted identifiers, letting a malicious server read client files
published 2026-10-29 10 d ago modified 2026-11-03 5 d ago also GHSA-fhx5-2xqw-2cgm , EUVD-2026-113382
- cvss
- 5.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 23%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- maven org.mariadb.jdbc:mariadb-java-client 3.3.7, 3.4.5, 3.5.11
- mariadb-java-client openSUSE Tumbleweed 3.5.11-1.1
opensuse advisories openSUSE-SU-2026:12401-1
- github.com/mariadb-corporation/mariadb-connector-j@4d2f800 commit
- github.com/mariadb-corporation/mariadb-connector-j@5812e0c commit
- github.com/mariadb-corporation/mariadb-connector-j@a4891f8 commit
- github.com/mariadb-corporation/mariadb-connector-j/releases/tag/3.3.7 release
- github.com/mariadb-corporation/mariadb-connector-j/releases/tag/3.4.5 release
- github.com/mariadb-corporation/mariadb-connector-j/releases/tag/3.5.11 release
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-119210 updated cvss 5.9
org.mariadb.jdbc/mariadb-java-client: MariaDB Connector/J: Information disclosure via bypass of local file validation
-
Red Hat build of Debezium 3 mariadb-java-client 3.5.3.redhat-00001 Red Hat Build of Keycloak rhbk/keycloak-rhel9, mariadb-java-client 3.5.3.redhat-00001affected: workaround, no fix available “Fix deferred”
-
Red Hat build of Quarkus mariadb-java-client 3.5.3.redhat-00001affected: workaround, no fix available
-
Red Hat Enterprise Linux 8 Judy, galera, mariadb, mariadb-pam, mariadb-test, mariadb-backup, +8 more Red Hat Enterprise Linux 9 mariadb-java-client 3.4.0-2.el10 Red Hat Enterprise Linux 10 mariadb-java-client 3.4.0-2.el10 Red Hat OpenShift AI (RHOAI) rhoai/odh-trustyai-service-rhel9affected: workaround, no fix available “Fix deferred”
-
Red Hat OpenStack Platform 13 (Queens) mariadb, mariadb-libs, mariadb-test, mariadb-common, mariadb-config, mariadb-errmsg, +3 moreaffected: workaround, no fix planned “Out of support scope”
-
Red Hat Satellite 6 candlepin, candlepin-selinuxaffected: workaround, no fix available “Fix deferred”
-
Red Hat Hardened Images mariadb10.11 10.11.18-4.1.2.hum1not affected: component not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 5 d ago
Exploit prediction
0.30% chance of exploitation in the next 30 days, higher than 23% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N |
| GitHub | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.mariadb.jdbc:mariadb-java-client | >=3.0.0, <3.3.7 >=3.4.0, <3.4.5 >=3.5.0, <3.5.11 |
3.3.7 3.4.5 3.5.11 |
Affected products
- mariadb-corporation mariadb-connector-j
Classification
References
-
github.com
/mariadb-corporation/mariadb-connector-j/commit/4d2f8002399949ed7f138e9c0b75b69229538120
web
-
github.com
/mariadb-corporation/mariadb-connector-j/commit/5812e0ca7574c3934915179b76f2e819a556d099
web
-
github.com
/mariadb-corporation/mariadb-connector-j/commit/a4891f877f1c885a573194771c1ed0aacec0ce1d
web
-
github.com
/mariadb-corporation/mariadb-connector-j/security/advisories/GHSA-fhx5-2xqw-2cgm
web
-
github.com
/mariadb-corporation/mariadb-connector-j/releases/tag/3.3.7
web
-
github.com
/mariadb-corporation/mariadb-connector-j/releases/tag/3.4.5
web
-
github.com
/mariadb-corporation/mariadb-connector-j/releases/tag/3.5.11
web
-
nvd.nist.gov
/vuln/detail/CVE-2026-119210
advisory
-
github.com
/mariadb-corporation/mariadb-connector-j
package
Sources
- CVE List CVE-2026-119210
- GitHub Advisory GHSA-fhx5-2xqw-2cgm
- NVD CVE-2026-119210
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.