Skip to content
Fencer Intel
low 3.7

CVE-2026-61700 json

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

published last mo. modified last mo. also GHSA-wxmm-q36w-r9xj , EUVD-2026-81903

cvss
3.7
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 30%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven org.mariadb.jdbc:mariadb-java-client 2.7.14, 3.3.5, 3.4.3, 3.5.9
  • mariadb-connector-java Debian 14 2.7.15-1

debian advisories DEBIAN-CVE-2026-61700

Is CVE-2026-61700 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-61700 updated cvss 3.7

org.mariadb.jdbc/mariadb-java-client: MariaDB Connector/J: Information disclosure via server-initiated LOCAL INFILE requests

  • Red Hat Hardened Images mariadb10.11 10.11.18-3.hum1
    not affected: component not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
last mo.

Exploit prediction

0.37% chance of exploitation in the next 30 days, higher than 30% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 3.7 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
GitHub 3.1 3.7 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
maven org.mariadb.jdbc:mariadb-java-client
<2.7.14
>=3.0.0, <3.3.5
>=3.4.0, <3.4.3
>=3.5.0, <3.5.9
2.7.14
3.3.5
3.4.3
3.5.9

Affected products

  • mariadb-corporation mariadb-connector-j

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.