CVE-2026-61700

published 17 Sep 2026 · updated 16 Nov 2026

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

3.7LowCVSS 3.7EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
MariaDB<2.7.14, >=3.0.0 <3.3.5, >=3.4.0 <3.4.3, >=3.5.0 <3.5.9

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-61700 severity on Zeptric[![CVE-2026-61700](https://zeptric.io/badge/cve/CVE-2026-61700.svg)](https://zeptric.io/cve/CVE-2026-61700)