| Name | 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. |
| Source | CVE (at NVD; CERT, ENISA, LWN, oss-sec, fulldisc, Debian ELTS, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more) |
Vulnerable and fixed packages
The table below lists information on source packages.
| Source Package | Release | Version | Status |
|---|
| rabbitmq-server (PTS) | bookworm, bookworm (security) | 3.10.8-1.1+deb12u1 | fixed |
| trixie | 4.0.5-6+deb13u2 | fixed |
| forky | 4.3.2-4 | vulnerable |
| sid | 4.3.2-5 | vulnerable |
The information below is based on the following data on fixed versions.
Notes
[trixie] - rabbitmq-server <not-affected> (Vulnerable code not present, only affects 4.2.x and later)
[bookworm] - rabbitmq-server <not-affected> (Vulnerable code not present, only affects 4.2.x and later)
https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-2rf7-f6r6-8rwh