# CVE-2026-119277: MariaDB Connector/J: Rogue server can make the client read past the packet through server-declared 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-119277?

CVE-2026-119277 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.11, decoders for OK packet session-state blocks, column definition packets, text row data, or binary row data used server-declared lengths without confirming that the requested bytes remained in the receive buffer. The decoders could position reads, create sub-buffers, or decode strings beyond the packet boundary. A malicious or compromised server, or a machine-in-the-middle attacker, could trigger unchecked ArrayIndexOutOfBoundsException or IllegalArgumentException failures inside JDBC calls and terminate connection handling. This issue is fixed in versions 3.3.7, 3.4.5, and 3.5.11.

Weakness: CWE-130 (Improper Handling of Length Parameter Inconsistency), CWE-125 (Out-of-bounds Read)

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


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

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

## Is CVE-2026-119277 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-119277 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-119277 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-119277/ (Markdown: https://insights.sbomify.com/CVE-2026-119277/index.md)
```

## Sources

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

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