Vulnerability 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.
CVSS Score
LOW
Related Weaknesses (CWE)
References
- https://github.com/mariadb-corporation/mariadb-connector-j/commit/0205d8be947918
- https://github.com/mariadb-corporation/mariadb-connector-j/releases/tag/3.5.9
- https://github.com/mariadb-corporation/mariadb-connector-j/security/advisories/G
FAQ
What is CVE-2026-61700?
CVE-2026-61700 is a vulnerability with a CVSS score of 3.7 (LOW). 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 LO...
How severe is CVE-2026-61700?
CVE-2026-61700 has been rated LOW with a CVSS base score of 3.7/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-61700?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.