Bug 2536132 (CVE-2026-61700) - CVE-2026-61700 org.mariadb.jdbc/mariadb-java-client: MariaDB Connector/J: Information disclosure via server-initiated LOCAL INFILE requests
Summary: CVE-2026-61700 org.mariadb.jdbc/mariadb-java-client: MariaDB Connector/J: Inf...
Keywords:
Status: NEW
Alias: CVE-2026-61700
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-09-17 16:06 UTC by OSIDB Bzimport
Modified: 2026-10-19 16:26 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-09-17 16:06:35 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.