Quick answers
- Is CVE-2026-119276 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-119276 being exploited in the wild.
- How severe is CVE-2026-119276?
- Medium severity, with a CVSS score of 5.9, published 29 October 2026.
- Which products and versions are affected?
- MariaDB Connector/J 3.0.0 to 3.3.6, 3.4.0 to 3.4.4, 3.5.0 to 3.5.10; org.mariadb.jdbc:mariadb-java-client (Maven) >= 3.0.0, < 3.3.7, ECOSYSTEM:introduced=3.0.0,fixed=3.3.7.
- Is there a fix for CVE-2026-119276?
- Yes. org.mariadb.jdbc:mariadb-java-client (Maven): upgrade to 3.3.7 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-119276 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-119276?
- Check whether you run MariaDB Connector/J or org.mariadb.jdbc:mariadb-java-client (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- org.mariadb.jdbc:mariadb-java-client (Maven): upgrade to 3.3.7 or later
# set org.mariadb.jdbc:mariadb-java-client to 3.3.7 in your pom.xml or build.gradle
Technical details
The vulnerability exists in the OkPacket.parse() and OkPacket.parseWithInfo() code paths when CLIENT_SESSION_TRACK capability negotiation is enabled. The parser reads server-declared lengths from the OK packet's info field and session-state variable names/values, then allocates byte arrays before validating that the declared bytes remain in the packet. A network-based attacker controlling the database server can send malformed OK packets with exaggerated length declarations to trigger repeated heap allocations, exhausting client memory.
Affected products
- MariaDB Connector/J 3.0.0 to 3.3.6, 3.4.0 to 3.4.4, 3.5.0 to 3.5.10
Identifiers
- CVE-2026-119276
- GHSA-h599-m3w5-9m7x
Timeline
- 2026-10-29: disclosed