# CVE-2026-93560: Io.netty/netty-codec-stomp: netty: stomp codec content-length long-to-int truncation causes infinite decode loop dos

> A remote attacker can cause a Denial of Service by sending a crafted STOMP frame with an oversized content-length header, triggering an infinite decode loop.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Sep 2026
- **Updated:** 22 Sep 2026
- **Also known as:** DEBIAN-CVE-2026-93560, GHSA-258j-9683-m467, UBUNTU-CVE-2026-93560

## What is CVE-2026-93560?

CVE-2026-93560 is a high-severity vulnerability in Red Hat Fuse 7, published on 18 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A flaw was found in the Netty STOMP codec. A remote attacker could send a specially crafted STOMP frame with a content-length header exceeding the maximum integer value. This integer truncation vulnerability could lead to an infinite decode loop, causing a Denial of Service (DoS) by exhausting memory and CPU resources.

Weakness: CWE-1035

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


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

Upgrade to a fixed version.

## Is CVE-2026-93560 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93560 is a high-severity vulnerability in Red Hat Fuse 7, published on 18 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-93560 in the wild and no public exploit code.

Affected product: Red Hat Fuse 7. 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-93560/ (Markdown: https://insights.sbomify.com/CVE-2026-93560/index.md)
```

## Sources

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

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