EXPOSURES › CVE-2026-67237
CVE-2026-67237
CRITICALCVE-2026-67237 in RabbitMQ allows unescaped token content to execute JavaScript in the management UI when OAuth is enabled.
RabbitMQ versions 4.2.0 through 4.2.8 and 4.3.2 failed to escape bearer tokens or access_token cookies inserted into OAuth bootstrap JavaScript, enabling remote code execution in the management UI. DIB organizations must patch to 4.2.8 or 4.3.2 immediately, as the management endpoint is exposed before authentication when OAuth is enabled, creating a high-risk attack surface for supply-chain and messaging infrastructure.
Shame score — A critical unpatched vulnerability in a widely deployed messaging broker allowed remote code execution via a simple cookie manipulation, demonstrating severe negligence in input validation and authentication bypass.
▸ RECOMMENDED ACTION Remote code execution — patch the affected products on priority.
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.
| PRODUCT | STATUS |
|---|---|
| Clarity Broadcom |
Authorized |
| General Support Systems (GSS) Broadcom |
Authorized |
| Rally Broadcom |
Authorized |
| Symantec Gov Cloud Security (GCS) Broadcom |
In Process |