CVE-2026-66071: CWE-400: Uncontrolled Resource Consumption in rabbitmq rabbitmq-server
RabbitMQ is a messaging and streaming broker. From 3.13.0 until 3.13.15 and 4.0.22 and 4.1.11 and 4.2.6 and 4.3.1, Atom exhaustion: OAuth2 JWT tag: scope values. extractscopes/1 parses scopes of the form .tag: and calls rabbitdatacoercion:toatom() to convert to a tag atom. The token signature is verified first, so the attacker cannot forge scopes , but in IdP configurations where scope content is user-influenced, each login with a novel tag value leaks one In deployments where users can influence the scopes included in their IdP-issued JWT rabbitmqauthbackendoauth2 enabled IdP permits attacker-influenced scope values in signed tokens. This issue is fixed in versions 3.13.15 and 4.0.22 and 4.1.11 and 4.2.6 and 4.3.1.
AI Analysis
Technical Summary
RabbitMQ server versions 3.13.0 through 3.13.14 and certain 4.x versions prior to 4.0.22, 4.1.11, 4.2.6, and 4.3.1 are vulnerable to uncontrolled resource consumption (CWE-400) via atom exhaustion. The vulnerability arises in the OAuth2 JWT scope parsing function extractscopes/1, which converts scope tag values to atoms using rabbitdatacoercion:toatom(). Although token signatures are verified preventing forgery, in IdP configurations where scope content is user-influenced, each login with a novel tag value leaks one atom, potentially exhausting system resources. This can lead to denial of service conditions. The vulnerability is addressed by the vendor in the specified fixed versions.
Potential Impact
An attacker able to influence scope values in IdP-issued JWT tokens can cause atom exhaustion on the RabbitMQ server, leading to uncontrolled resource consumption and potential denial of service. The vulnerability does not allow token forgery or privilege escalation but can degrade service availability.
Mitigation Recommendations
This vulnerability is fixed in rabbitmq-server versions 3.13.15, 4.0.22, 4.1.11, 4.2.6, and 4.3.1. Users should upgrade to these or later versions to remediate the issue. No additional mitigations are indicated by the vendor advisory. Patch status is confirmed by the vendor's version fixes.
CVE-2026-66071: CWE-400: Uncontrolled Resource Consumption in rabbitmq rabbitmq-server
Description
RabbitMQ is a messaging and streaming broker. From 3.13.0 until 3.13.15 and 4.0.22 and 4.1.11 and 4.2.6 and 4.3.1, Atom exhaustion: OAuth2 JWT tag: scope values. extractscopes/1 parses scopes of the form .tag: and calls rabbitdatacoercion:toatom() to convert to a tag atom. The token signature is verified first, so the attacker cannot forge scopes , but in IdP configurations where scope content is user-influenced, each login with a novel tag value leaks one In deployments where users can influence the scopes included in their IdP-issued JWT rabbitmqauthbackendoauth2 enabled IdP permits attacker-influenced scope values in signed tokens. This issue is fixed in versions 3.13.15 and 4.0.22 and 4.1.11 and 4.2.6 and 4.3.1.
CVSS v4.0
Score 6.0medium
Affected software
rabbitmq
rabbitmq-server
pkg:github/rabbitmq/rabbitmq-serverRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
RabbitMQ server versions 3.13.0 through 3.13.14 and certain 4.x versions prior to 4.0.22, 4.1.11, 4.2.6, and 4.3.1 are vulnerable to uncontrolled resource consumption (CWE-400) via atom exhaustion. The vulnerability arises in the OAuth2 JWT scope parsing function extractscopes/1, which converts scope tag values to atoms using rabbitdatacoercion:toatom(). Although token signatures are verified preventing forgery, in IdP configurations where scope content is user-influenced, each login with a novel tag value leaks one atom, potentially exhausting system resources. This can lead to denial of service conditions. The vulnerability is addressed by the vendor in the specified fixed versions.
Potential Impact
An attacker able to influence scope values in IdP-issued JWT tokens can cause atom exhaustion on the RabbitMQ server, leading to uncontrolled resource consumption and potential denial of service. The vulnerability does not allow token forgery or privilege escalation but can degrade service availability.
Mitigation Recommendations
This vulnerability is fixed in rabbitmq-server versions 3.13.15, 4.0.22, 4.1.11, 4.2.6, and 4.3.1. Users should upgrade to these or later versions to remediate the issue. No additional mitigations are indicated by the vendor advisory. Patch status is confirmed by the vendor's version fixes.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-07-23T23:25:28.897Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6ab6a25af7a7c54106018e23
Added to database: 09/25/2026, 16:33:30 UTC
Last enriched: 09/25/2026, 16:49:10 UTC
Last updated: 09/26/2026, 02:44:15 UTC
Views: 13
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.