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

Published Oct 29, 2026 CVSS 3.1 · 5.9 Medium EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The connector’s validation routine for local file paths incorrectly accepts file names that appear inside quoted identifiers, string literals, or comments in a LOAD DATA LOCAL INFILE statement. An attacker who can influence the server’s responses—such as a compromised database server or a man‑in‑the‑middle attacker—can embed an arbitrary client‑host file name in metadata or updatable‑result queries. When allowLocalInfile is enabled, the connector then attempts to read that file from the client machine, thereby exposing any readable client data to the attacker.

Affected Systems

MariaDB Connector/J versions 3.0.0 up to but excluding 3.3.7, 3.4.5, and 3.5.11 are affected. This library is used by Java applications that connect to MariaDB or MySQL databases.

Risk and Exploitability

The CVSS score of 5.9 indicates moderate severity. The EPSS score of < 1% indicates a very low likelihood of exploitation, and the vulnerability is not listed in the CISA KEV catalog. Attacks require control or compromise of the database server or interception of traffic to supply malicious identifiers; once a connection with allowLocalInfile enabled is established, the attacker can read any file readable by the client process, resulting in data leakage.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade MariaDB Connector/J to version 3.3.7, 3.4.5, or 3.5.11, where the file name validation is fixed.
  • Disable the allowLocalInfile property in the JDBC connection string or application configuration to block the execution of LOAD DATA LOCAL INFILE commands.
  • Audit and restrict the use of DatabaseMetaData methods outside trusted contexts, ensuring that metadata information is not derived from untrusted server responses.

Generated by OpenCVE AI on November 2, 2026 at 14:59 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-fhx5-2xqw-2cgm MariaDB Connector/J: LOAD DATA LOCAL INFILE file check could be satisfied by text inside quoted identifiers, letting a malicious server read client files
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Mariadb
Mariadb mariadb-connector-j
Mariadb-corporation
Mariadb-corporation mariadb-connector-j
Vendors & Products Mariadb
Mariadb mariadb-connector-j
Mariadb-corporation
Mariadb-corporation mariadb-connector-j
Type Values Removed Values Added
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.
Title MariaDB Connector/J: LOAD DATA LOCAL INFILE file check could be satisfied by text inside quoted identifiers, letting a malicious server read client files
Weaknesses CWE-20
CWE-73
References
Metrics cvssV3_1

{'score': 5.9, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N'}

Weaknesses
  • CWE-20

    Improper Input Validation

  • CWE-625

    Permissive Regular Expression

  • CWE-73

    External Control of File Name or Path

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Nov 3, 2026, 4:45 PM
Reserved
Oct 29, 2026, 4:04 PM
Status
Awaiting Analysis
Published
Oct 29, 2026, 9:17 PM
Modified
Nov 3, 2026, 5:18 PM
Severity
Moderate
Public date
Oct 29, 2026, 8:45 PM