# CVE-2026-67237: RabbitMQ reflected XSS in OAuth bootstrap management UI

Source: https://junglewise.ai/threats/cve-2026-67237-rabbitmq-is-a-messaging-and-streaming-broker-from-4-2-0-until-4-2  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-25. Updated: 2026-09-26  
License: CC BY 4.0 with a link back

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](https://junglewise.ai/threats/technologies/rabbitmq-rabbitmq). Vendors: [RabbitMQ](https://junglewise.ai/threats/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

- [https://github.com/rabbitmq/rabbitmq-server/commit/5cd6d841d84450324a4613501ed917d98828af23](https://github.com/rabbitmq/rabbitmq-server/commit/5cd6d841d84450324a4613501ed917d98828af23)
- [https://github.com/rabbitmq/rabbitmq-server/commit/a8041d528c1a71af4cb75ade247ed082fe6b83fb](https://github.com/rabbitmq/rabbitmq-server/commit/a8041d528c1a71af4cb75ade247ed082fe6b83fb)

## Related threats

- [RabbitMQ OAuth privilege escalation via stale token tags](https://junglewise.ai/threats/cve-2026-67420-rabbitmq-is-a-messaging-and-streaming-broker-from-3-13-0-until-3)
- [RabbitMQ topic exchange denial of service via duplicate matchers](https://junglewise.ai/threats/cve-2026-67419-rabbitmq-is-a-messaging-and-streaming-broker-prior-to-4-3-5-an)
- [RabbitMQ Shovel denial of service via atom exhaustion](https://junglewise.ai/threats/cve-2026-67415-rabbitmq-is-a-messaging-and-streaming-broker-from-4-2-0-until-4-2)
- [RabbitMQ MQTT loopback user bypass via PROXY Protocol](https://junglewise.ai/threats/cve-2026-67411-rabbitmq-is-a-messaging-and-streaming-broker-from-3-13-0-until-3)
- [RabbitMQ OAuth2 client secret exposure via unauthenticated endpoint](https://junglewise.ai/threats/cve-2026-67410-rabbitmq-is-a-messaging-and-streaming-broker-from-4-2-0-until-4-3)