---
id: "CVE-2026-119210"
kind: "vulnerability"
aliases: ["CVE-2026-119210"]
title: "MariaDB Connector/J: crafted identifiers let a server read client files"
severity: "medium"
cvss: 5.9
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["java", "jdbc", "mariadb", "mysql", "package"]
not_affected_if: ["default-config", "local-infile-disabled", "trusted-database-server"]
published_at: "2026-10-29T21:17:20+00:00"
first_seen_at: "2026-10-29T21:26:51+00:00"
updated_at: "2026-10-29T21:28:51+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-119210", "first_seen_at": "2026-10-29T21:26:51+00:00"}]
---

# MariaDB Connector/J: crafted identifiers let a server read client files

MariaDB Connector/J, the Java driver for MariaDB and MySQL, can be tricked by a malicious or compromised database server into requesting a local file from the client machine. With allowLocalInfile enabled, the driver then streams any readable client-host file named in the crafted identifiers.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the connector version in the project build file (for example the mariadb-java-client entry in `pom.xml` or `build.gradle`) and see whether it falls in an affected range.
- Search the application configuration for `allowLocalInfile=true` in JDBC URLs.

## Fix

- Upgrade to `3.3.7`, `3.4.5`, or `3.5.11`, matching your current release line.

## Timeline

- 2026-10-29T21:26:51+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-119210

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_