Is CVE-2026-67421 exploited in the wild?

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

How severe is CVE-2026-67421?

Informational severity, published 25 September 2026.

Which products and versions are affected?

VMware RabbitMQ 3.13.0 through 3.13.18, 4.0.0 through 4.0.23, 4.1.0 through 4.1.14, 4.2.0 through 4.2.9, 4.3.0 through 4.3.4.

Is there a fix for CVE-2026-67421?

A patch was published on 2026-09-25: Fixes available in RabbitMQ 3.13.19, 4.0.24, 4.1.15, 4.2.10, 4.3.5 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-67421 attacked?

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

Am I affected by CVE-2026-67421?

Check whether you run VMware 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-67421: RabbitMQ Management XSS via queue name in OAuth UI

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

RabbitMQ's web-based management console contains a cross-site scripting (XSS) vulnerability in the OAuth login flow that allows an attacker to steal an administrator's session credentials. An attacker with basic queue permissions can craft a malicious queue name containing HTML/JavaScript; when an administrator tries to view messages from that queue, the attacker's code executes in the admin's browser and exfiltrates their OAuth authorization token to an attacker-controlled server.

Technologies: VMware RabbitMQ. Vendors: VMware.

Quick answers

Is CVE-2026-67421 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-67421 being exploited in the wild.
How severe is CVE-2026-67421?: Informational severity, published 25 September 2026.
Which products and versions are affected?: VMware RabbitMQ 3.13.0 through 3.13.18, 4.0.0 through 4.0.23, 4.1.0 through 4.1.14, 4.2.0 through 4.2.9, 4.3.0 through 4.3.4.
Is there a fix for CVE-2026-67421?: A patch was published on 2026-09-25: Fixes available in RabbitMQ 3.13.19, 4.0.24, 4.1.15, 4.2.10, 4.3.5 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-67421 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-67421?: Check whether you run VMware 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 Management plugin's OAuth login template fails to properly escape queue names when rendering AMQP authorization errors as HTML. An attacker with queue configure permission crafts a queue name containing a base HTML element to retarget relative URL refreshes. Due to missing CSP directives (base-uri, connect-src) and permissive CORS on an attacker endpoint, the victim's Authorization header is leaked when the admin clicks "Get Message(s)" on the malicious queue.

Affected products

VMware RabbitMQ 3.13.0 through 3.13.18, 4.0.0 through 4.0.23, 4.1.0 through 4.1.14, 4.2.0 through 4.2.9, 4.3.0 through 4.3.4

Timeline

2026-09-25: disclosed: CVE-2026-67421 published
2026-09-25: patched: Fixes available in RabbitMQ 3.13.19, 4.0.24, 4.1.15, 4.2.10, 4.3.5

References

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