# CVE-2026-93452: snappy-java through 1.1.10.8 Buffer Overflow in Snappy.compress

> Attackers can cause JVM termination by supplying incompressible data to snappy-java, leading to a buffer overflow and denial of service.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/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:** 17 Sep 2026
- **Updated:** 8 Oct 2026
- **Also known as:** CLEANSTART-2026-HC59767, CLEANSTART-2026-RU43979, CLEANSTART-2026-UM59263, CLEANSTART-2026-ZO24294, ECHO-88ee-645b-e5d6, GHSA-pm27-vjq7-f5fv, UBUNTU-CVE-2026-93452

## What is CVE-2026-93452?

CVE-2026-93452 is a high-severity memory corruption vulnerability in xerial snappy-java, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

snappy-java through 1.1.10.8 contains a buffer overflow vulnerability in Snappy.compress(ByteBuffer, ByteBuffer) that writes past the end of the destination buffer. Attackers can supply incompressible data that exceeds the destination buffer's remaining capacity, corrupting off-heap memory and causing JVM termination.

Weakness: CWE-787 (Out-of-bounds Write)

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


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

Upgrade to a fixed version.

## Is CVE-2026-93452 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93452 is a high-severity memory corruption vulnerability in xerial snappy-java, published on 17 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-93452 exists.

Affected product: xerial snappy-java. 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-93452/ (Markdown: https://insights.sbomify.com/CVE-2026-93452/index.md)
```

## Sources

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

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