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
broadcom: rabbitmq server
References5
- github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-2r… Vendor Advisory
- github.com/rabbitmq/rabbitmq-server/commit/5cd6d841d84450324a46… Patch
- github.com/rabbitmq/rabbitmq-server/commit/a8041d528c1a71af4cb7… Patch
- github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.8 Release NotesPatch
- github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.2 Release NotesPatch
Metrics
- CVSS 3.1
-
9.3
CRITICAL
Score source: NVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N - CVSS 4.0
-
7.5
HIGH
Score source: CNA
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X - EPSS — exploit probability
- 0% percentile: 39 · as of 9 November 2026
- CWE
- CWE-79
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.