# CVE-2026-119279: MariaDB Connector/J: Length-encoded integers larger than Integer.MAX_VALUE were truncated before being used as lengths


- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 29 Oct 2026
- **Updated:** 29 Oct 2026

## What is CVE-2026-119279?

CVE-2026-119279 is a medium-severity vulnerability in mariadb-corporation mariadb-connector-j, published on 29 Oct 2026. 

### Official 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.

Weakness: CWE-190 (Integer Overflow or Wraparound), CWE-130 (Improper Handling of Length Parameter Inconsistency)

## Which versions are affected by CVE-2026-119279?


## How do I fix CVE-2026-119279?

No fix has been published for CVE-2026-119279 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-119279 being exploited?

There is no known exploitation of CVE-2026-119279 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-119279 and fix it if it is affected.

What it is: CVE-2026-119279 is a medium-severity vulnerability in mariadb-corporation mariadb-connector-j, published on 29 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-119279 in the wild and no public exploit code.

Affected product: mariadb-corporation mariadb-connector-j. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-119279/ (Markdown: https://insights.sbomify.com/CVE-2026-119279/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-119279
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-119279
- OSV: https://osv.dev/vulnerability/CVE-2026-119279

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-119279/
Summaries are generated and may contain mistakes; the official description above is the record.