CVE-2026-61700
MariaDB Connector/J is used to connect applications developed in …
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 now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/mariadb-corporation/mariadb-connector-j/commit/0205d8be947918566cd9ce5a9db14954
- github.com/mariadb-corporation/mariadb-connector-j/releases/tag/3.5.9
- github.com/mariadb-corporation/mariadb-connector-j/security/advisories/GHSA-wxmm-q36w-r9xj
- github.com/advisories/GHSA-wxmm-q36w-r9xj
- nvd.nist.gov/vuln/detail/CVE-2026-61700
- cve.org/CVERecord?id=CVE-2026-61700
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.