Is CVE-2026-67239 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-67239 being exploited in the wild.

How severe is CVE-2026-67239?

Informational severity, published 25 September 2026.

Which products and versions are affected?

RabbitMQ 3.13.0–3.13.17, 4.0.0–4.0.22, 4.1.0–4.1.13, 4.2.0–4.2.8, 4.3.0–4.3.2.

Is there a fix for CVE-2026-67239?

A patch was published on 2026-07-20: Fixed in versions 3.13.18, 4.0.23, 4.1.14, 4.2.9, 4.3.3 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-67239 attacked?

It is attacked over the network, in a hosted service.

Am I affected by CVE-2026-67239?

Check whether you run RabbitMQ at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-67239: RabbitMQ stored XSS in stream-management UI via TLS peer-certificate DN

CVE-2026-67239 · Severity: info · Published 2026-09-25

RabbitMQ is a messaging broker that administrators manage through a web-based UI. A stored cross-site scripting vulnerability allows an attacker with a trusted TLS certificate to inject malicious scripts into the stream connection management interface by crafting a certificate with a specially-formatted name. When an operator views the affected interface, the attacker's script executes in their browser, potentially allowing account takeover or session hijacking.

Technologies: RabbitMQ. Vendors: RabbitMQ.

Quick answers

Is CVE-2026-67239 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-67239 being exploited in the wild.
How severe is CVE-2026-67239?: Informational severity, published 25 September 2026.
Which products and versions are affected?: RabbitMQ 3.13.0–3.13.17, 4.0.0–4.0.22, 4.1.0–4.1.13, 4.2.0–4.2.8, 4.3.0–4.3.2.
Is there a fix for CVE-2026-67239?: A patch was published on 2026-07-20: Fixed in versions 3.13.18, 4.0.23, 4.1.14, 4.2.9, 4.3.3 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-67239 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-67239?: Check whether you run RabbitMQ at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability is a stored XSS in the stream-management UI where peer certificate subject and issuer DNs are rendered without proper HTML escaping (using raw <% %> instead of safe fmtstring()). RFC4514 backslash-escaping bypasses basic filters; an attacker can inject payloads like <img //>. Exploitation requires non-default configuration: a TLS stream listener with peer verification enabled, and an attacker-obtained certificate signed by a CA the listener trusts. The attack triggers when an operator views the stream connection detail page.

Affected products

RabbitMQ RabbitMQ 3.13.0–3.13.17, 4.0.0–4.0.22, 4.1.0–4.1.13, 4.2.0–4.2.8, 4.3.0–4.3.2

Timeline

2026-09-25: disclosed
2026-07-20: patched: Fixed in versions 3.13.18, 4.0.23, 4.1.14, 4.2.9, 4.3.3

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.