Rabbitmq server: RabbitMQ is a messaging and streaming broker. (CVE-2026-66071)
Description
CVE-2026-66071 is a medium severity vulnerability in RabbitMQ server versions from 3.13.0 up to 3.13.15 and several 4.x versions. It involves atom exhaustion caused by parsing OAuth2 JWT scope values influenced by users in certain IdP configurations. The vulnerability allows leaking of atom tags during login with novel scope values. This issue is fixed in RabbitMQ versions 3.13.15, 4.0.22, 4.1.11, 4.2.6, and 4.3.1.
CVSS v3.1
Score 6.5medium
Affected software
pkg:deb/ubuntu/rabbitmq-server?arch=source&distro=esm-infra-legacy/xenialpkg:deb/ubuntu/rabbitmq-server?arch=source&distro=esm-infra/bionicpkg:deb/ubuntu/rabbitmq-server?arch=source&distro=esm-infra/focalpkg:deb/ubuntu/rabbitmq-server?arch=source&distro=jammypkg:deb/ubuntu/rabbitmq-server?arch=source&distro=noblepkg:deb/ubuntu/rabbitmq-server?arch=source&distro=resoluteRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
RabbitMQ server versions 3.13.0 through 3.13.15 and 4.0.0 through 4.3.1 are affected by an atom exhaustion vulnerability (CVE-2026-66071) related to the OAuth2 JWT scope parsing mechanism. The function extractscopes/1 parses scope values of the form .tag: and converts them to atoms via rabbitdatacoercion:toatom(). Because the token signature is verified, attackers cannot forge scopes, but in Identity Provider (IdP) configurations where scope content is user-influenced, each login with a novel tag value leaks one atom tag. This can lead to atom exhaustion, potentially causing denial of service. The vulnerability is fixed in versions 3.13.15, 4.0.22, 4.1.11, 4.2.6, and 4.3.1.
Potential Impact
The vulnerability can cause atom exhaustion in RabbitMQ servers when processing OAuth2 JWT tokens with user-influenced scope values. This may lead to denial of service (application crash or resource exhaustion). There is no impact on confidentiality or integrity as token signatures are verified and scopes cannot be forged. The attack requires an IdP configuration that permits attacker-influenced scope values in signed tokens.
Mitigation Recommendations
Upgrade RabbitMQ to versions 3.13.15, 4.0.22, 4.1.11, 4.2.6, or 4.3.1 where this vulnerability is fixed. No other mitigations are indicated. Patch status is confirmed fixed in these versions.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- UBUNTU-CVE-2026-66071
- Osv Schema Version
- 1.7.0
- Ecosystems
- ["Ubuntu:Pro:16.04:LTS","Ubuntu:Pro:18.04:LTS","Ubuntu:Pro:20.04:LTS","Ubuntu:22.04:LTS","Ubuntu:24.04:LTS","Ubuntu:26.04:LTS"]
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6ad3f5b12cdf04f656662826
Added to database: 10/17/2026, 22:24:49 UTC
Last enriched: 10/18/2026, 00:09:07 UTC
Last updated: 10/18/2026, 00:09:07 UTC
Views: 2
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.