Summary
MariaDB Connector/J does not enforce allowLocalInfile=false on server-initiated LOCAL INFILE requests
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 itsLOAD 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 COM_QUERY.
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 INFILEon potentially
sensitive files (credentials, exports, configs) and connects over
an untrusted network. allowLocalInfile=falseis supposed to disable this entire
mechanism as a defense-in-depth measure, but the flag is ignored.
Credit
Reported by tharavel
Impact
The security guarantee of allowLocalInfile=false is not upheld,
but practical exploitation requires both a MitM/rogue server and an
application that actively uses LOCAL INFILE on sensitive data.
CVE-2026-61700 has a CVSS score of 3.7 (Low). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.7.14, 3.3.5, 3.4.3, 3.5.9); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
org.mariadb.jdbc:mariadb-java-client to 2.7.14 or later; org.mariadb.jdbc:mariadb-java-client to 3.3.5 or later; org.mariadb.jdbc:mariadb-java-client to 3.4.3 or later; org.mariadb.jdbc:mariadb-java-client to 3.5.9 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-61700? CVE-2026-61700 is a low-severity security vulnerability in org.mariadb.jdbc:mariadb-java-client (maven), affecting versions < 2.7.14. It is fixed in 2.7.14, 3.3.5, 3.4.3, 3.5.9.
- How severe is CVE-2026-61700? CVE-2026-61700 has a CVSS score of 3.7 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of org.mariadb.jdbc:mariadb-java-client are affected by CVE-2026-61700? org.mariadb.jdbc:mariadb-java-client (maven) versions < 2.7.14 is affected.
- Is there a fix for CVE-2026-61700? Yes. CVE-2026-61700 is fixed in 2.7.14, 3.3.5, 3.4.3, 3.5.9. Upgrade to this version or later.
- Is CVE-2026-61700 exploitable, and should I be worried? Whether CVE-2026-61700 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-61700 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-61700?
- Upgrade
org.mariadb.jdbc:mariadb-java-clientto 2.7.14 or later - Upgrade
org.mariadb.jdbc:mariadb-java-clientto 3.3.5 or later - Upgrade
org.mariadb.jdbc:mariadb-java-clientto 3.4.3 or later - Upgrade
org.mariadb.jdbc:mariadb-java-clientto 3.5.9 or later
- Upgrade