CVE-2026-67237: broadcom rabbitmq_server

CVSS 9.3 (critical) · published 2026-09-25

RabbitMQ is a messaging and streaming broker. From 4.2.0 until 4.2.8 and 4.3.2, set_token_auth/2 inserted a bearer token from the Authorization header or access_token cookie into OAuth bootstrap JavaScript without escaping, allowing attacker-controlled token content to execute JavaScript in the management UI origin. The endpoint is exposed before authentication only when management.oauth_enabled is true, and exploitation through the cookie path additionally requires the attacker to plant an access_token cookie on the management host. This issue is fixed in versions 4.2.8 and 4.3.2.

Affected products (NVD): broadcom rabbitmq_server

Fixed in (NVD): 4.2.8, 4.3.2

Weakness: CWE-79

Source: NVD CVE-2026-67237

References

• https://github.com/rabbitmq/rabbitmq-server/commit/5cd6d841d84450324a4613501ed917d98828af23
• https://github.com/rabbitmq/rabbitmq-server/commit/a8041d528c1a71af4cb75ade247ed082fe6b83fb
• https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.8
• https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.2
• https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-2rf7-f6r6-8rwh

Check your software

Connect an AI agent to the FixLane MCP server or ask the Telegram bot to check what you have installed against incidents with a verified fixed version.