# CVE-2026-90560: zstd-jni 1.2.0 through 1.5.7-13 Out-of-Bounds Read via ZstdDictDecompress

> Attackers can trigger an out-of-bounds read in zstd-jni by supplying invalid offsets, potentially causing JVM termination or memory disclosure.

- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** CLEANSTART-2026-OH53916, CLEANSTART-2026-PB88860, CLEANSTART-2026-UX53854, CLEANSTART-2026-WJ34335, CLEANSTART-2026-YH52150, CLEANSTART-2026-YT94531, DEBIAN-CVE-2026-90560, GHSA-392q-wrgq-6wmj, UBUNTU-CVE-2026-90560

## What is CVE-2026-90560?

CVE-2026-90560 is a high-severity memory corruption vulnerability in luben zstd-jni, published on 12 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

zstd-jni versions 1.2.0 through 1.5.7-13 contain an out-of-bounds read vulnerability in the ZstdDictDecompress constructor because offset and length arguments are never validated against the dictionary array bounds. Attackers can supply arbitrary offset or length values to read memory past the end of the supplied array, potentially causing JVM termination.

Weakness: CWE-125 (Out-of-bounds Read)

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


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

Upgrade to a fixed version.

## Is CVE-2026-90560 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-90560 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-90560 is a high-severity memory corruption vulnerability in luben zstd-jni, published on 12 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-90560 exists.

Affected product: luben zstd-jni. 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-90560/ (Markdown: https://insights.sbomify.com/CVE-2026-90560/index.md)
```

## Sources

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

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