WaratekVRT Sign in

CVE-2026-61700

Severity3.7 Low CVSS 3.1
Fixed in2.7.14, 3.3.5, 3.4.3, 3.5.9
WeaknessImproper access control (CWE-284)
Published17 Sep 2026
Updated23 Sep 2026

Published 58 days ago. NVD often adds the list of affected products days or weeks after a CVE is published, and the other sources we check lag too. The scope and status here may change.

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.

Exploitation status

No public exploit

No exploit has been reported in the sources we check.

  • CISA KEV not listed
  • VulnCheck KEV not listed
  • CISA Vulnrichment exploitation: none
  • Indexed PoC none indexed
  • EPSS 0.37% chance in 30 days

Waratek protection

No exploit published

Within Waratek scope. In the sources we check, nobody has published exploit code for this CVE or reported it being exploited.

A public code fix exists: mariadb-corporation/mariadb-connector-j 0205d8b.

  • Protection none
  • Action unverified
  • Review automated Upstream data
  • Record active
Decided by Medium or Low severity, no CISA or VulnCheck KEV listing, no PoC clearing the evidence bar, no CISA verdict, no Oracle advisory
Finding This CVE is LOW severity, is not listed in CISA KEV or VulnCheck KEV, has no public exploit or PoC in any indexed source, carries no CISA Vulnrichment finding of a demonstrated exploit, and is not part of an Oracle Critical Patch Update. None of the signals that would put it in front of an engineer is present, and the volume of CVEs below that bar is too great to take one at a time, so no rule is written for it. This is a decision about what we act on, not a finding that the CVE is harmless — a patch may well be derivable, and a low-severity defect can still be one link in a longer chain.
Candidate fix https://github.com/mariadb-corporation/mariadb-connector-j/commit/0205d8be947918566cd9ce5a9db149541bbc8dee : a commit: the change itself

Affected software and releases

Maven packages

Affected and fixed versions, from OSV.dev
PackageIntroducedFixedLast affected
org.mariadb.jdbc:mariadb-java-client 0 2.7.14 unbounded
org.mariadb.jdbc:mariadb-java-client 3.0.0 3.3.5 unbounded
org.mariadb.jdbc:mariadb-java-client 3.4.0 3.4.3 unbounded
org.mariadb.jdbc:mariadb-java-client 3.5.0 3.5.9 unbounded

Products and versions

1 product, 4 version entries
SourceVendorProductSchemeAffected versions
osv org.mariadb.jdbc mariadb-java-client generic < 2.7.14 · ≥ 3.0.0 and < 3.3.5 · ≥ 3.4.0 and < 3.4.3 · ≥ 3.5.0 and < 3.5.9

References

URLTags
https://github.com/mariadb-corporation/mariadb-connector-j/commit/0205d8be947918566cd9ce5a9db149541bbc8dee commit
https://github.com/mariadb-corporation/mariadb-connector-j/security/advisories/GHSA-wxmm-q36w-r9xj WEB
https://github.com/mariadb-corporation/mariadb-connector-j PACKAGE
https://github.com/mariadb-corporation/mariadb-connector-j/releases/tag/3.5.9 WEB

Timeline

Published2026-09-17By the CVE Program.
NVD record modified2026-09-23NVD's own last-modified date for this record.