Vulnerability 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.
Related Weaknesses (CWE)
References
- https://github.com/rabbitmq/rabbitmq-server/commit/5cd6d841d84450324a4613501ed91
- https://github.com/rabbitmq/rabbitmq-server/commit/a8041d528c1a71af4cb75ade247ed
- 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-8
FAQ
What is CVE-2026-67237?
CVE-2026-67237 is a documented vulnerability. 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 JavaS...
How severe is CVE-2026-67237?
CVSS scoring is not yet available for CVE-2026-67237. Check NVD for updates.
Is there a patch for CVE-2026-67237?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.