Summary
MariaDB Connector/J: Length-encoded integers larger than Integer.MAX_VALUE were truncated before being used as lengths
MariaDB Connector/J narrowed 8-byte length-encoded integers received from the
server to int without validation. A rogue or MitM server can send a value aboveInteger.MAX_VALUE whose truncation becomes a negative or arbitrary length.
Details
The protocol encodes lengths as length-encoded integers, whose 8-byte form the
decoder (readLength() and readIntLengthEncodedNotNull()) returned as(int) readLong(). A value above Integer.MAX_VALUE therefore wrapped to a
negative or unrelated int, used afterwards as a length to size allocations or
reads, which ended in NegativeArraySizeException, out-of-bounds exceptions or
oversized allocations.
The fix rejects any length-encoded value that does not fit a non-negative int
with an explicit error.
Credit
Reported by fg0x0
Impact
Availability only: a malicious or compromised server, or a MitM, can crash the
client's connection handling with unchecked exceptions or drive oversized
allocations. Exploitation requires control of the server side of the connection;
no authentication bypass, confidentiality or integrity impact.
An arithmetic operation produces a value that exceeds the integer type's maximum, causing it to wrap to an unexpected small value. Typical impact: incorrect size calculations leading to heap overflows or logic errors.
CVE-2026-119279 has a CVSS score of 5.9 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.3.7, 3.4.5, 3.5.10); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
org.mariadb.jdbc:mariadb-java-client to 3.3.7 or later; org.mariadb.jdbc:mariadb-java-client to 3.4.5 or later; org.mariadb.jdbc:mariadb-java-client to 3.5.10 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-119279? CVE-2026-119279 is a medium-severity integer overflow or wraparound vulnerability in org.mariadb.jdbc:mariadb-java-client (maven), affecting versions >= 3.0.0, < 3.3.7. It is fixed in 3.3.7, 3.4.5, 3.5.10. An arithmetic operation produces a value that exceeds the integer type's maximum, causing it to wrap to an unexpected small value.
- How severe is CVE-2026-119279? CVE-2026-119279 has a CVSS score of 5.9 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of org.mariadb.jdbc:mariadb-java-client are affected by CVE-2026-119279? org.mariadb.jdbc:mariadb-java-client (maven) versions >= 3.0.0, < 3.3.7 is affected.
- Is there a fix for CVE-2026-119279? Yes. CVE-2026-119279 is fixed in 3.3.7, 3.4.5, 3.5.10. Upgrade to this version or later.
- Is CVE-2026-119279 exploitable, and should I be worried? Whether CVE-2026-119279 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-119279 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-119279?
- Upgrade
org.mariadb.jdbc:mariadb-java-clientto 3.3.7 or later - Upgrade
org.mariadb.jdbc:mariadb-java-clientto 3.4.5 or later - Upgrade
org.mariadb.jdbc:mariadb-java-clientto 3.5.10 or later
- Upgrade