# CVE-2026-93564: Denial of service in Red Hat AMQ Broker 7

> Remote attackers can cause memory exhaustion and denial of service by sending crafted HAProxy PROXY-v2 headers to applications using the Netty codec.

- **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:** 15 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-93564, GHSA-74qm-9qc5-ff4g, UBUNTU-CVE-2026-93564

## What is CVE-2026-93564?

CVE-2026-93564 is a high-severity denial of service vulnerability in Red Hat AMQ Broker 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 Netty. A reference-count leak in the HAProxy PROXY-v2 message decoder allows a remote, unauthenticated attacker to send specially crafted PROXY-protocol v2 headers. This can lead to memory exhaustion, resulting in a Denial of Service (DoS) for the affected system.

Weakness: CWE-1035

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


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

Apply the vendor's patch.

## Is CVE-2026-93564 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93564 is a high-severity denial of service vulnerability in Red Hat AMQ Broker 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-93564 in the wild and no public exploit code.

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

## Sources

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

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