CVE-2026-119279
| Severity | 5.9 Medium CVSS 3.1 |
|---|---|
| Fixed in | 3.3.7, 3.4.5, 3.5.10 |
| Weakness | Integer overflow (CWE-190) |
| Published | 29 Oct 2026 |
| Updated | 3 Nov 2026 |
Published 16 days ago. NVD often adds the list of affected products days or weeks after a CVE is published, and the other sources we check lag too. The scope and status here may change.
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.10, the ReadableByteBuf.readLength() and ReadableByteBuf.readIntLengthEncodedNotNull() methods narrowed the protocol's unsigned 8-byte length-encoded integer to a Java int without checking that the value fit a non-negative integer. Values above Integer.MAX_VALUE could wrap to a negative or unrelated length that downstream allocation and read paths used. A malicious or compromised server, or a machine-in-the-middle attacker, could trigger NegativeArraySizeException, out-of-bounds failures, or oversized allocation behavior in client connection handling. This issue is fixed in versions 3.3.7, 3.4.5, and 3.5.10.
CWE-130
Exploitation status
No public exploit
No exploit has been reported in the sources we check.
Exploitation status
- CISA KEV not listed
- VulnCheck KEV not listed
- CISA Vulnrichment exploitation: none
- Indexed PoC none indexed
- EPSS 0.35% chance in 30 days
Waratek protection
Within Waratek scope. In the sources we check, nobody has published exploit code for this CVE or reported it being exploited.
A public code fix exists: mariadb-corporation/mariadb-connector-j 30d4a88.
- Protection none
- Action unverified
- Review automated Upstream data
- Record active
| Decided by | Medium or Low severity, no CISA or VulnCheck KEV listing, no PoC clearing the evidence bar, no CISA verdict, no Oracle advisory |
|---|---|
| Finding | This CVE is MEDIUM severity, is not listed in CISA KEV or VulnCheck KEV, has no public exploit or PoC in any indexed source, carries no CISA Vulnrichment finding of a demonstrated exploit, and is not part of an Oracle Critical Patch Update. None of the signals that would put it in front of an engineer is present, and the volume of CVEs below that bar is too great to take one at a time, so no rule is written for it. This is a decision about what we act on, not a finding that the CVE is harmless — a patch may well be derivable, and a low-severity defect can still be one link in a longer chain. |
| Candidate fix | https://github.com/mariadb-corporation/mariadb-connector-j/commit/30d4a883377a9b7762e02ee2c60d54567032ab99 : a commit: the change itself |
Affected software and releases
Maven packages
Affected and fixed versions, from OSV.dev| Package | Introduced | Fixed | Last affected |
|---|---|---|---|
org.mariadb.jdbc:mariadb-java-client |
3.0.0 | 3.3.7 |
unbounded |
org.mariadb.jdbc:mariadb-java-client |
3.4.0 | 3.4.5 |
unbounded |
org.mariadb.jdbc:mariadb-java-client |
3.5.0 | 3.5.10 |
unbounded |
Products and versions
1 product, 3 version entries| Source | Vendor | Product | Scheme | Affected versions |
|---|---|---|---|---|
| osv | org.mariadb.jdbc | mariadb-java-client | generic | ≥ 3.0.0 and < 3.3.7 · ≥ 3.4.0 and < 3.4.5 · ≥ 3.5.0 and < 3.5.10 |
References
Timeline
Timeline
| Published | 2026-10-29 | By the CVE Program. |
|---|---|---|
| NVD record modified | 2026-11-03 | NVD's own last-modified date for this record. |