CVE-2026-119276 · GHSA-h599-m3w5-9m7x
MariaDB Connector/J: Rogue server can drive large heap allocations from server-declared lengths in OK packets
- Risk score
- 40/100
- CVSS
- 5.9 v3.1
- Published
- 29 Oct 2026
Open in the live forecast Today's forecast
What to know
- What it is
- MariaDB Connector/J is used to connect applications developed in Java to MariaDB and MySQL databases. From 3.0.0 until 3.3.7, 3.4.5, and 3.5.11, when CLIENT_SESSION_TRACK was negotiated, the OkPacket.parse() and OkPacket.parseWithInfo() paths allocated byte arrays using server-declared lengths for the OK packet info f…
- Affected
- org.mariadb.jdbc:mariadb-java-client (maven) >= 3.0.0, < 3.3.7; org.mariadb.jdbc:mariadb-java-client (maven) >= 3.4.0, < 3.4.5; org.mariadb.jdbc:mariadb-java-client (maven) >= 3.5.0, < 3.5.11
- Fix
- Upgrade org.mariadb.jdbc:mariadb-java-client to 3.3.7 or 3.4.5 or 3.5.11 (whichever matches your release line) or later.
- Exploitation
- No known exploitation
Story map
At a glance
org.mariadb.jdbc:mariadb-java-client: Yellow, plan it in. MariaDB Connector/J is used to connect applications developed in Java to MariaDB and MySQL databases. From 3.0.0 until 3.3.7, 3.4.5, and 3.5.11, when CLIENT_SESSION_TRACK was negotiated, the OkPacket.parse() and OkPacket.parseWithInfo() paths allocated byte arrays using server-declared lengths for the OK packet info f…
The flaws
- CVE-2026-119276: MariaDB Connector/J: Rogue server can drive large heap allocations from server-declared lengths in OK packets (CVSS 5.9)
- CVE-2026-119210: MariaDB Connector/J: LOAD DATA LOCAL INFILE file check could be satisfied by text inside quoted identifiers, letting a malicious server read client files (CVSS 5.9)
- CVE-2026-119279: MariaDB Connector/J: Length-encoded integers larger than Integer.MAX_VALUE were truncated before being used as lengths (CVSS 5.9)
- CVE-2026-119281: MariaDB Connector/J: Server could switch character_set_results away from UTF-8 without the client noticing (CVSS 5.9)
The fix
Upgrade org.mariadb.jdbc:mariadb-java-client: 3.3.7 · 3.4.5 · 3.5.11 · 3.5.10 or later on your release line
Who is exposed: org.mariadb.jdbc:mariadb-java-client (maven) >= 3.0.0, < 3.3.7; org.mariadb.jdbc:mariadb-java-client (maven) >= 3.4.0, < 3.4.5; org.mariadb.jdbc:mariadb-java-client (maven) >= 3.5.0, < 3.5.11
Where it stands
- No known exploitation
Connects to
- Same weakness: CWE-130 (CWE-130). 15 other warnings in 30 days
Why it is Yellow
- CVSS 5.9 medium
- On your watchlist: Maven
Affected packages
| Package | Ecosystem | Vulnerable | Fixed in |
|---|---|---|---|
| org.mariadb.jdbc:mariadb-java-client | maven | >= 3.0.0, < 3.3.7 | 3.3.7 |
| org.mariadb.jdbc:mariadb-java-client | maven | >= 3.4.0, < 3.4.5 | 3.4.5 |
| org.mariadb.jdbc:mariadb-java-client | maven | >= 3.5.0, < 3.5.11 | 3.5.11 |
References
- https://github.com/mariadb-corporation/mariadb-connector-j/commit/b9e1ee8d9b4d820d70719504cdfd5c97f1aede5f
- https://github.com/mariadb-corporation/mariadb-connector-j/commit/beb445fcf9294113878fc05ac77f0efdf0596ac6
- https://github.com/mariadb-corporation/mariadb-connector-j/commit/ea8c7b6537e50053444188a9a3fd9cae99550f56
- https://github.com/mariadb-corporation/mariadb-connector-j/releases/tag/3.3.7
- https://github.com/mariadb-corporation/mariadb-connector-j/releases/tag/3.4.5
- https://github.com/mariadb-corporation/mariadb-connector-j/releases/tag/3.5.11
- https://github.com/mariadb-corporation/mariadb-connector-j/security/advisories/GHSA-h599-m3w5-9m7x
- https://github.com/advisories/GHSA-h599-m3w5-9m7x
- https://nvd.nist.gov/vuln/detail/CVE-2026-119276
- https://github.com/advisories/GHSA-h599-m3w5-9m7x
Original description
MariaDB Connector/J is used to connect applications developed in Java to MariaDB and MySQL databases. From 3.0.0 until 3.3.7, 3.4.5, and 3.5.11, when CLIENT_SESSION_TRACK was negotiated, the OkPacket.parse() and OkPacket.parseWithInfo() paths allocated byte arrays using server-declared lengths for the OK packet info field and session-state variable names and values before confirming that the bytes remained in the packet. A malicious or compromised server, or a machine-in-the-middle attacker, could send a small OK packet declaring a much larger length and repeatedly force attacker-controlled heap allocations before the subsequent copy failed. This could create garbage-collection pressure or an OutOfMemoryError in the client application. This issue is fixed in versions 3.3.7, 3.4.5, and 3.5.11.
Last activity 30 Oct 2026. Patch Forecast updates every hour.