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.
CVE-2026-66071
This medium-severity CVE scores 6.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (25th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 6.0
- EG Score
- 6.0MEDIUMmedium confidence
- EG Risk
- 27EG Risk 27/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity60% × 45%Exploitation0% × 40%Automatability0% × 15%CISA SSVC: Track at every mission impact level.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.3%
- EPSS %ILE
- 25th
- KEV
- Not listed
CISA SSVCTrack at every mission impact level.
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
September 25, 2026
Last Modified
September 28, 2026
Advisory Details (5)
Auto-updated Sep 25, 2026RabbitMQ 4.3.1
Patch available: rabbitmq/rabbitmq-server v4.3.1
https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.1RabbitMQ 4.2.6
Patch available: rabbitmq/rabbitmq-server v4.2.6
https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.6commit c5690583a537 (rabbitmq/rabbitmq-server)
Fix landed in rabbitmq/rabbitmq-server commit c5690583a537 — awaiting tagged release
https://github.com/rabbitmq/rabbitmq-server/commit/c5690583a53789a3bf00cca508b43e8246db0d11commit 9a44124d9c93 (rabbitmq/rabbitmq-server)
Fix landed in rabbitmq/rabbitmq-server commit 9a44124d9c93 — awaiting tagged release
https://github.com/rabbitmq/rabbitmq-server/commit/9a44124d9c932d6fc7d2a3b945e5a143e547bcb6Atom exhaustion: OAuth2 JWT tag: scope values · Advisory · rabbitmq/rabbitmq-server · GitHub
https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-89p2-f5cv-x5cgVendor Advisories for CVE-2026-66071(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | rabbitmq-server4-3-main-4.3.6-1.hum1 | 2026-09-15 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Additional Vendor Advisories
(1)
Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.
Data Freshness Timeline
(refreshed 16× in last 7d / 23× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-10-04 09:01 UTCEG score recompute
- 2026-10-04 09:01 UTCVendor advisory
- 2026-10-03 14:26 UTCEPSS rescore
- 2026-10-03 09:58 UTCEG score recompute
- 2026-10-03 09:58 UTCVendor advisory
- 2026-10-02 17:56 UTCEPSS rescore
- 2026-10-02 10:53 UTCEG score recompute
- 2026-10-02 10:53 UTCVendor advisory
- 2026-10-01 19:50 UTCEPSS rescore
- 2026-10-01 11:51 UTCEG score recompute
- 2026-09-30 15:03 UTCEPSS rescore
- 2026-09-30 12:49 UTCEG score recompute
- 2026-09-29 13:46 UTCEG score recompute
- 2026-09-28 14:44 UTCEG score recompute
- 2026-09-28 13:51 UTCEPSS rescore
- 2026-09-27 16:45 UTCEG score recompute
- 2026-09-26 17:44 UTCEG score recompute
- 2026-09-26 15:59 UTCEPSS rescore
- 2026-09-25 18:40 UTCEG score recompute
- 2026-09-25 18:03 UTCEG score recompute
- 2026-09-25 17:37 UTCEG score recompute
- 2026-09-25 16:24 UTCEG score recompute
- 2026-09-25 16:24 UTCMITRE cvelistV5first tracked
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat:RHSA-2026:67552
Frequently asked(5)
What is CVE-2026-66071?
When was CVE-2026-66071 disclosed?
Is CVE-2026-66071 actively exploited?
What is the CVSS score of CVE-2026-66071?
How do I remediate CVE-2026-66071?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-66071
Is Your Infrastructure Affected by CVE-2026-66071?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.