MariaDB Connector/J does not enforce allowLocalInfile=false on server-initiated LOCAL INFILE requests

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

3.7 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N

EPSS

• CVE-2026-61700: 0.37% estimated exploitation activity in the next 30 days; percentile 30.53 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary MariaDB Connector/J does not enforce allowLocalInfile=false when processing server-initiated LOCAL INFILE requests (protocol packet type 0xfb). However, exploitation is constrained: the server can only request the exact filename the client already included in its LOAD DATA LOCAL INFILE query, it cannot redirect to arbitrary paths. Details When a client executes LOAD DATA LOCAL INFILE '/path/to/file', the connector sends the filename to the server as part of the COMQUERY. A rogue or MitM server responds with a 0xfb packet echoing that same filename. The connector, without checking allowLocalInfile, transmits the file content. The bypass is therefore limited to the file the application itself intended to load. The attacker cannot escalate to other files (e.g. /etc/passwd) unless the application's own query targets them. The real-world risk is: - An application that uses LOAD DATA LOCAL INFILE on potentially sensitive files (credentials, exports, configs) and connects over an…

Published by the source

17 Sep 2026, 16:29 UTC

Last modified by the source

17 Sep 2026, 16:45 UTC

Source last checked

26 Oct 2026, 16:55 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-wxmm-q36w-r9xj

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-wxmm-q36w-r9xj

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

# Patch Next advisory brief: CVE-2026-61700

Advisory: MariaDB Connector/J does not enforce allowLocalInfile=false on server-initiated LOCAL INFILE requests
IDs: CVE-2026-61700, GHSA-wxmm-q36w-r9xj
Record: https://patchnext.com/advisories/cve-2026-61700 (revision 2, source checked 26 Oct 2026, 16:55 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 3.7)
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.9, 3.4.3, 3.3.5, 2.7.14. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.mariadb.jdbc:mariadb-java-client: affected < 2.7.14; >= 3.0.0, < 3.3.5; >= 3.4.0, < 3.4.3; >= 3.5.0, < 3.5.9; fixed in 3.5.9, 3.3.5, 2.7.14, 3.4.3

## 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://osv.dev/vulnerability/GHSA-wxmm-q36w-r9xj (OSV record GHSA-wxmm-q36w-r9xj lists affected ranges: Maven org.mariadb.jdbc:mariadb-java-client >=0 =3.0.0 =3.4.0 =3.5.0 <3.5.9 (fixed))
- Verified: https://github.com/advisories/GHSA-wxmm-q36w-r9xj (GitHub-reviewed advisory GHSA-wxmm-q36w-r9xj lists affected ranges: Maven org.mariadb.jdbc:mariadb-java-client >=0 =3.0.0 =3.4.0 =3.5.0 <3.5.9)

Commands are suggestions: review each one before running it.