# CVE-2026-93567: Security feature bypass in Red Hat AMQ Broker 7

> Attackers can bypass tunnel allow-lists and egress policies by manipulating Host headers in HTTP/1 CONNECT requests translated to HTTP/2.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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:** 19 Oct 2026
- **Also known as:** CLEANSTART-2026-IT87450, DEBIAN-CVE-2026-93567, GHSA-xf8w-rc87-x5gw, UBUNTU-CVE-2026-93567

## What is CVE-2026-93567?

CVE-2026-93567 is a high-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/2 codec. When converting HTTP/1 CONNECT requests to HTTP/2, the component incorrectly uses the Host header instead of the CONNECT authority-form request-target for the tunnel authority. A remote attacker can exploit this by supplying a different Host header, leading to a malformed HTTP/2 CONNECT request. This can bypass security controls such as tunnel allow-lists or egress policies, resulting in integrity loss.

Weakness: CWE-20 (Improper Input Validation)

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


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

Upgrade to a fixed version.

## Is CVE-2026-93567 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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