Vulnerabilities in pkg:maven/org.mariadb.jdbc/mariadb-java-client
PACKAGECVE-2026-61700 is a LOW (CVSS 3.7) remote code execution vulnerability (CWE-284: Improper Access Control) affecting Mariadb java client libraries in the Maven ecosystem. The issue involves mariadb connector/j does not enforce allowlocalinfile=false on server-initiated local infile requests. Remediation is available by upgrading affected packages to version 2.7.14, 3.3.5, 3.4.3, 3.5.9.
pkg:maven/org.mariadb.jdbc/mariadb-java-client
Vulnerability advisories affecting package pkg:maven/org.mariadb.jdbc/mariadb-java-client. Select an advisory below to view technical details or fixes.
| Advisory ID | CVE / NVD | Severity | Summary |
|---|---|---|---|
| GHSA-wxmm-q36w-r9xj | CVE-2026-61700 | LOW | MariaDB Connector/J does not enforce allowLocalInfile=false on server-initiated LOCAL INFILE requests |
| GHSA-xvr9-35cr-46v9 | CVE-2026-55858 | MODERATE | org.mariadb.jdbc:mariadb-java-client has Inappropriate Encoding for Output Context |
| GHSA-qxvw-fvwx-5cp7 | CVE-2026-55857 | MODERATE | org.mariadb.jdbc:mariadb-java-client has Cleartext Transmission of Sensitive Information and Insufficiently Protected Credentials |
| GHSA-g9jj-cgmh-9f38 | CVE-2026-55856 | MODERATE | MariaDB has cleartext password disclosure to a MITM on the initial-handshake |
CVE-2026-61700 at a Glance
Security Impact
CVSS: 3.7
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N).
How to Fix CVE-2026-61700
To remediate this vulnerability, upgrade all affected Mariadb java client dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
<dependency>
<groupId>org.mariadb.jdbc</groupId>
<artifactId>mariadb-java-client</artifactId>
<version>2.7.14</version>
</dependency>
<dependency>
<groupId>org.mariadb.jdbc</groupId>
<artifactId>mariadb-java-client</artifactId>
<version>3.3.5</version>
</dependency>
<dependency>
<groupId>org.mariadb.jdbc</groupId>
<artifactId>mariadb-java-client</artifactId>
<version>3.4.3</version>
</dependency>
<dependency>
<groupId>org.mariadb.jdbc</groupId>
<artifactId>mariadb-java-client</artifactId>
<version>3.5.9</version>
</dependency>
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
mvn dependency:tree -Dincludes=org.mariadb.jdbc
How to Check if You Are Affected
To determine whether your Java application is affected by CVE-2026-61700, inspect your build dependencies using the Maven Dependency Plugin:
mvn dependency:tree -Dincludes=org.mariadb.jdbc
Analyze the terminal output to locate any version of Mariadb java client in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.7.14), your application is affected.
Note: The mvn dependency:tree -Dincludes=org.mariadb.jdbc command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-284: Improper Access Control, where the product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. In Mariadb java client, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-61700 Affected Mariadb java client Versions
4 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
org.mariadb.jdbc:mariadb-java-client
|
Maven |
< 2.7.14
|
2.7.14
|
|
org.mariadb.jdbc:mariadb-java-client
|
Maven |
≥ 3.0.0
< 3.3.5
|
3.3.5
|
|
org.mariadb.jdbc:mariadb-java-client
|
Maven |
≥ 3.4.0
< 3.4.3
|
3.4.3
|
|
org.mariadb.jdbc:mariadb-java-client
|
Maven |
≥ 3.5.0
< 3.5.9
|
3.5.9
|
References
Frequently Asked Questions
What is CVE-2026-61700?
Which Mariadb java client versions are affected?
What version fixes CVE-2026-61700?
Is mariadb-java-client affected?
What is the CVSS score of CVE-2026-61700?
What CWE is associated with CVE-2026-61700?
How can I check Maven dependencies for CVE-2026-61700?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-wxmm-q36w-r9xj",
"modified" : "2026-09-17T16:29:54Z",
"published" : "2026-09-17T16:29:53Z",
"aliases" : [ "CVE-2026-61700" ],
"summary" : "MariaDB Connector/J does not enforce allowLocalInfile=false on server-initiated LOCAL INFILE requests",
"details" : "## Summary\n\nMariaDB Connector/J does not enforce `allowLocalInfile=false` when \nprocessing server-initiated LOCAL INFILE requests (protocol packet \ntype `0xfb`). However, exploitation is constrained: the server can \nonly request the exact filename the client already included in its \n`LOAD DATA LOCAL INFILE` query, it cannot redirect to arbitrary paths.\n\n## Details\n\nWhen a client executes `LOAD DATA LOCAL INFILE '/path/to/file'`, the \nconnector sends the filename to the server as part of the COM_QUERY. \nA rogue or MitM server responds with a `0xfb` packet echoing that \nsame filename. The connector, without checking `allowLocalInfile`, \ntransmits the file content.\n\nThe bypass is therefore limited to the file the application itself \nintended to load. The attacker cannot escalate to other files \n(e.g. `/etc/passwd`) unless the application's own query targets them.\n\nThe real-world risk is:\n- An application that uses `LOAD DATA LOCAL INFILE` on potentially \n sensitive files (credentials, exports, configs) and connects over \n an untrusted network.\n- `allowLocalInfile=false` is supposed to disable this entire \n mechanism as a defense-in-depth measure, but the flag is ignored.\n\n## Impact\n\nThe security guarantee of `allowLocalInfile=false` is not upheld, \nbut practical exploitation requires both a MitM/rogue server and an \napplication that actively uses LOCAL INFILE on sensitive data.\n\n## Credit\n\nReported by tharavel",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Maven",
"name" : "org.mariadb.jdbc:mariadb-java-client"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "2.7.14"
} ]
} ]
}, {
"package" : {
"ecosystem" : "Maven",
"name" : "org.mariadb.jdbc:mariadb-java-client"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "3.0.0"
}, {
"fixed" : "3.3.5"
} ]
} ]
}, {
"package" : {
"ecosystem" : "Maven",
"name" : "org.mariadb.jdbc:mariadb-java-client"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "3.4.0"
}, {
"fixed" : "3.4.3"
} ]
} ]
}, {
"package" : {
"ecosystem" : "Maven",
"name" : "org.mariadb.jdbc:mariadb-java-client"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "3.5.0"
}, {
"fixed" : "3.5.9"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/mariadb-corporation/mariadb-connector-j/security/advisories/GHSA-wxmm-q36w-r9xj"
}, {
"type" : "WEB",
"url" : "https://github.com/mariadb-corporation/mariadb-connector-j/commit/0205d8be947918566cd9ce5a9db149541bbc8dee"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/mariadb-corporation/mariadb-connector-j"
}, {
"type" : "WEB",
"url" : "https://github.com/mariadb-corporation/mariadb-connector-j/releases/tag/3.5.9"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-284" ],
"severity" : "LOW",
"github_reviewed" : true,
"github_reviewed_at" : "2026-09-17T16:29:53Z",
"nvd_published_at" : null
}
}