Critical severity9.3NVD Advisory· Published Sep 25, 2026· Updated Oct 20, 2026
CVE-2026-67237
CVE-2026-67237
Description
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
3- Range: 4.2.0 - 4.2.8, 4.3.2
- cpe:2.3:a:broadcom:rabbitmq_server:*:*:*:*:*:*:*:*Range: >=4.2.0,<4.2.8
Patches
Vulnerability mechanics
References
5- github.com/rabbitmq/rabbitmq-server/commit/5cd6d841d84450324a4613501ed917d98828af23nvdPatch
- github.com/rabbitmq/rabbitmq-server/commit/a8041d528c1a71af4cb75ade247ed082fe6b83fbnvdPatch
- github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.8nvdRelease NotesPatch
- github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.2nvdRelease NotesPatch
- github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-2rf7-f6r6-8rwhnvdVendor Advisory
News mentions
1- RabbitMQ: 25 Vulnerabilities Disclosed Together, Highlighting Auth, UI, and DoS RisksVypr Intelligence · Sep 25, 2026