Impact
An attacker can influence the contents of OAuth2 JWT scopes that contain a ".tag:" prefix. When RabbitMQ parses these scopes, it converts each unique tag value into an Erlang atom. Because atoms are stored in a finite table that grows with each new untrusted value, a high volume of distinct tags can fill the table and exhaust system memory, causing the broker to crash or become unresponsive. This results in a denial‑of‑service attack. The weaknesses are identified as CWE‑400 and CWE‑770.
Affected Systems
RabbitMQ Server versions 3.13.0 through 3.13.14, 4.0.0 through 4.0.21, 4.1.0 through 4.1.10, 4.2.0 through 4.2.5, and 4.3.0 are affected. The problem is triggered when the rabbitmqauthbackendoauth2 backend is enabled and the IdP permits user‑controlled scope values in signed JWTs. All clients connected to the compromised broker can experience service disruption.
Risk and Exploitability
The CVSS score of 6 denotes medium severity. The EPSS score of 0.00342 indicates a very low probability of exploitation, with no public exploits reported yet. The vulnerability is not listed in the CISA KEV catalog. An attacker would need to supply a signed JWT with novel ".tag:" scope values, which requires an IdP that allows such content.
OpenCVE Enrichment