# CVE-2026-93573: Other in Red Hat AMQ Broker 7

> Remote attackers can bypass HTTP transfer-encoding validation in Netty to perform request smuggling, bypassing security controls and desynchronizing request processing.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **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-93573, GHSA-xvf3-842c-j48x, UBUNTU-CVE-2026-93573

## What is CVE-2026-93573?

CVE-2026-93573 is a medium-severity 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's HTTP/1.1 decoder. This vulnerability allows a remote attacker to bypass `Transfer-Encoding` header validation by splitting the `Transfer-Encoding` field across multiple headers, with the last field containing a non-final transfer coding like `gzip` or `deflate`. This bypass can lead to HTTP request smuggling, enabling attackers to bypass security controls, desynchronize request processing, or cause requests to be processed in an unintended context.

Weakness: CWE-444 (Inconsistent Interpretation of HTTP Requests)

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


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

Upgrade to a fixed version.

## Is CVE-2026-93573 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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