Answer in brief
CVE-2026-61700 records a Low severity (CVSS 3.7) vulnerability in MariaDB Connector/J does not enforce allowLocalInfile=false on server-initiated LOCAL INFILE requests. The current sources do not mark it as known exploited. The current feed maps mariadb-corporation/mariadb-connector-j (generic), org.mariadb.jdbc:mariadb-java-client (maven), org.mariadb.jdbc:mariadb-java-client (maven), org.mariadb.jdbc:mariadb-java-client (maven) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 3.7. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps mariadb-corporation/mariadb-connector-j (generic), org.mariadb.jdbc:mariadb-java-client (maven), org.mariadb.jdbc:mariadb-java-client (maven), org.mariadb.jdbc:mariadb-java-client (maven) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| mariadb-corporation/mariadb-connector-jgeneric | < 2.7.14 || >= 3.0.0, < 3.3.5 || >= 3.4.0, < 3.4.3 || >= 3.5.0, < 3.5.9 | Not reported |
| org.mariadb.jdbc:mariadb-java-clientmaven | <2.7.14 | 2.7.14 |
| org.mariadb.jdbc:mariadb-java-clientmaven | >=3.0.0,<3.3.5 | 3.3.5 |
| org.mariadb.jdbc:mariadb-java-clientmaven | >=3.4.0,<3.4.3 | 3.4.3 |
| org.mariadb.jdbc:mariadb-java-clientmaven | >=3.5.0,<3.5.9 | 3.5.9 |
Published upstream
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 17, 2026
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.
Quoted source text, attributed separately from HOL analysis.