Is CVE-2026-67237 exploited in the wild?

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

How severe is CVE-2026-67237?

Informational severity, published 25 September 2026.

Which products and versions are affected?

RabbitMQ 4.2.0 to 4.2.7, 4.3.0 to 4.3.1.

Is there a fix for CVE-2026-67237?

A patch was published on 2026-09-25: Fixed in versions 4.2.8 and 4.3.2 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-67237 attacked?

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

Am I affected by CVE-2026-67237?

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-67237: RabbitMQ reflected XSS in OAuth bootstrap management UI

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

RabbitMQ is a messaging broker that manages connections and message routing. Versions 4.2.0 to 4.2.7 and 4.3.0-4.3.1 contain a cross-site scripting vulnerability in the management UI's OAuth login page. An attacker can inject malicious JavaScript by crafting a specially-formed Authorization header or by planting a cookie on the management host, allowing them to execute scripts with access to the management interface and potentially compromise administrative sessions.

Technologies: RabbitMQ. Vendors: RabbitMQ.

Quick answers

Is CVE-2026-67237 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-67237 being exploited in the wild.
How severe is CVE-2026-67237?: Informational severity, published 25 September 2026.
Which products and versions are affected?: RabbitMQ 4.2.0 to 4.2.7, 4.3.0 to 4.3.1.
Is there a fix for CVE-2026-67237?: A patch was published on 2026-09-25: Fixed in versions 4.2.8 and 4.3.2 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-67237 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-67237?: 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 set_token_auth/2 function in rabbit_mgmt_oauth_bootstrap.erl fails to escape bearer tokens from the Authorization header or access_token cookie before inserting them into OAuth bootstrap JavaScript, resulting in reflected XSS. The vulnerability requires management.oauth_enabled to be true; exploitation via the cookie vector additionally requires the attacker to plant an access_token cookie on the management host. The fix involves proper HTML/JavaScript escaping of token content before embedding in the page.

Affected products

RabbitMQ RabbitMQ 4.2.0 to 4.2.7, 4.3.0 to 4.3.1

Timeline

2026-09-25: disclosed
2026-09-25: patched: Fixed in versions 4.2.8 and 4.3.2

References

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