Skip to content

← Actionable
Medium, CVSS 5.9amended

MariaDB Connector/J: LOAD DATA LOCAL INFILE file check could be satisfied by text inside quoted identifiers, letting a malicious server read client files

CVE-2026-119210GHSA-fhx5-2xqw-2cgm

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (org.mariadb.jdbc:mariadb-java-client 3.5.11, 3.4.5, 3.3.7), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
5.9 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
  • CVE-2026-119210: 0.30% estimated exploitation activity in the next 30 days; percentile 23.12 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary MariaDB Connector/J checked a server's LOAD DATA LOCAL INFILE file request by searching the text of the command it had sent for `LOAD DATA LOCAL INFILE ' '`. The search also matched inside quoted identifiers, string literals and comments, so text returned by the server and re-used in a later query could satisfy it. A rogue or MitM server can read any file the client JVM can read.

Details When a server answers a command with a LOCAL INFILE request (`0xFB` packet), the connector opens the named file on the client host and streams it to the server, after verifying that the file corresponds to a `LOAD DATA LOCAL INFILE` of the command it sent (`ClientMessage.validateLocalFileName()`). That verification was a regular expression whose prefix accepted any character, so it answered "does the text appear anywhere in the SQL", including inside a backtick-quoted identifier. Several driver paths put identifiers returned by the server straight back into their next query:…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from osv record GHSA-fhx5-2xqw-2cgm

  2. Revision 1 · created ·

    Published from ghsa record GHSA-fhx5-2xqw-2cgm

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-119210

Advisory: MariaDB Connector/J: LOAD DATA LOCAL INFILE file check could be satisfied by text inside quoted identifiers, letting a malicious server read client files
IDs: CVE-2026-119210, GHSA-fhx5-2xqw-2cgm
Record: https://patchnext.com/advisories/cve-2026-119210 (revision 2, source checked 31 Oct 2026, 07:05 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.mariadb.jdbc:mariadb-java-client 3.5.11, 3.4.5, 3.3.7. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.mariadb.jdbc:mariadb-java-client: affected >= 3.0.0, < 3.3.7; >= 3.4.0, < 3.4.5; >= 3.5.0, < 3.5.11; fixed in 3.5.11, 3.3.7, 3.4.5

## Suggested inspection (read-only)
- Maven org.mariadb.jdbc:mariadb-java-client: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.mariadb.jdbc:mariadb-java-client.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-fhx5-2xqw-2cgm (GitHub-reviewed advisory GHSA-fhx5-2xqw-2cgm lists affected ranges: Maven org.mariadb.jdbc:mariadb-java-client >=3.0.0 =3.4.0 =3.5.0 <3.5.11)
- Verified: https://osv.dev/vulnerability/GHSA-fhx5-2xqw-2cgm (OSV record GHSA-fhx5-2xqw-2cgm lists affected ranges: Maven org.mariadb.jdbc:mariadb-java-client >=3.0.0 =3.4.0 =3.5.0 <3.5.11 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…