Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
3.7

MariaDB Connector/J may transmit local files despite disabled option

published 10 days ago
Summary

The Java library used to connect to MariaDB and MySQL servers can send a local file to the server even when the option to allow this is turned off. This occurs in versions prior to the latest releases and only matters if your application loads data over an untrusted network connection. Update the connector to version 2.7.14 or later (or the matching 3.x releases) to stop the unwanted file transmission.

What to do

The CVE record does not list a fixed version. Check the vendor's site or the advisory links below - a fix may already be released.

Affected software
Ecosystem VendorProductAffected versions
Docker Hardened Images:Debian:13 docker hardened images datahub-gms All versions
Docker Hardened Images:Debian:13 docker hardened images datahub-mce-consumer-fips All versions
Docker Hardened Images:Debian:13 docker hardened images datahub-mce-consumer All versions
Docker Hardened Images:Debian:13 docker hardened images datahub-upgrade All versions
Docker Hardened Images:Debian:13 docker hardened images liquibase-4 All versions
Docker Hardened Images:Debian:13 docker hardened images piraeus-server All versions
Original advisory text
MariaDB Connector/J is used to connect applications developed in Java to MariaDB and MySQL databases. Prior to 2.7.14…
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.
Fix within
Internet-facing 14 days
Internal 60 days
  • Not known to be exploited
  • Can be exploited automatically (estimated)
  • Gives an attacker partial control (estimated)
Severity
3.7 Low
Timeline
Published11 Nov 2026
Updated16 Nov 2026
First seen16 Nov 2026
Sources
Track software like this
Free during beta