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.

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - 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. (CVE-2026-61700)

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - 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. (CVE-2026-61700)

Note that Nessus relies on the presence of the package as reported by the vendor.

ID	Name	Product	Family	Type	Severity
462284	Echo: org.mariadb.jdbc:mariadb-java-client: security update to 2.7.14	Tenable Cloud Security	Echo Local Security Checks	Local	low
462284	Echo: org.mariadb.jdbc:mariadb-java-client: security update to 2.7.14	Tenable Self-Hosted Container Security	Echo Local Security Checks	Local	low
348202	Linux Distros Unpatched Vulnerability : CVE-2026-61700	Nessus	Misc.	Local	low

Detections

Analytics

CVE-2026-61700

low

Tenable Plugins

low

low

low