CVE-2026-67237

CRITICALNVD 9.39.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This critical-severity CVE scores 9.3 under NVD CVSS v3. EPSS exploit probability: 0.5% (39th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2026-87148 (ENISA EUVD)Source: ENISA EUVD

9.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 9.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
9.3
EG Score
9.3CRITICALmedium confidence
EG Risk
42
EG Risk 42/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity93% × 45%
Impact severity (EG Severity): CVSS 9.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
39th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.3): severity, escalated by confirmed exploitation. This CVE's 9.3 is its impact severity (EG Severity), not escalated.

EG Severity
9.3 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 25, 2026

Last Modified

October 20, 2026

Advisory Details (5)

Auto-updated Sep 25, 2026
Patch available. Sources: github, github_commit, github_release.
GitHub release Patch Available

RabbitMQ 4.3.2

Patch available: rabbitmq/rabbitmq-server v4.3.2

https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.2
GitHub release Patch Available

RabbitMQ 4.2.8

Patch available: rabbitmq/rabbitmq-server v4.2.8

https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.8
GitHub commit

commit a8041d528c1a (rabbitmq/rabbitmq-server)

Fix landed in rabbitmq/rabbitmq-server commit a8041d528c1a — awaiting tagged release

https://github.com/rabbitmq/rabbitmq-server/commit/a8041d528c1a71af4cb75ade247ed082fe6b83fb
GitHub commit

commit 5cd6d841d844 (rabbitmq/rabbitmq-server)

Fix landed in rabbitmq/rabbitmq-server commit 5cd6d841d844 — awaiting tagged release

https://github.com/rabbitmq/rabbitmq-server/commit/5cd6d841d84450324a4613501ed917d98828af23
GitHub advisoryMentions a patch (unverified)

Reflected XSS via the OAuth bootstrap JS endpoint · Advisory · rabbitmq/rabbitmq-server · GitHub

https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-2rf7-f6r6-8rwh

Vendor Advisories for CVE-2026-67237(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubunturabbitmq-server (3.8.3-0ubuntu0.3+esm2) @ focal2026-11-02ubuntu
redhatrabbitmq-server4-3-main-4.3.6-1.hum12026-09-15redhat

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.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
rabbitmq-server4.0.5-10 ... 4.3.0-3 (11 versions)
  • every version up to 4.3.2-1: fixed in 4.3.2-1
—

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 22× in last 7d / 77× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-02 04:53 UTCEG score recompute
  2. 2026-11-02 04:53 UTCVendor advisory
  3. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  4. 2026-11-01 06:17 UTCEG score recompute
  5. 2026-11-01 06:17 UTCVendor advisory
  6. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  7. 2026-10-31 07:40 UTCEG score recompute
  8. 2026-10-31 07:40 UTCVendor advisory
  9. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  10. 2026-10-30 09:03 UTCEG score recompute
  11. 2026-10-30 09:03 UTCVendor advisory
  12. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  13. 2026-10-29 10:27 UTCEG score recompute
  14. 2026-10-29 10:27 UTCVendor advisory
  15. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  16. 2026-10-28 11:50 UTCEG score recompute
  17. 2026-10-28 11:50 UTCVendor advisory
  18. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  19. 2026-10-27 13:07 UTCVendor advisory
  20. 2026-10-27 06:54 UTCEG score recompute
  21. 2026-10-27 06:54 UTCVendor advisory
  22. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  23. 2026-10-26 04:59 UTCEG score recompute
  24. 2026-10-26 04:59 UTCVendor advisory
  25. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.5% · 38th percentile
Show 71 more
  1. 2026-10-25 14:10 UTCEG score recompute
  2. 2026-10-25 06:23 UTCEG score recompute
  3. 2026-10-25 06:23 UTCVendor advisory
  4. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  5. 2026-10-24 07:46 UTCEG score recompute
  6. 2026-10-24 07:46 UTCVendor advisory
  7. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  8. 2026-10-23 09:05 UTCEG score recompute
  9. 2026-10-23 09:05 UTCVendor advisory
  10. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  11. 2026-10-22 10:25 UTCEG score recompute
  12. 2026-10-22 10:25 UTCVendor advisory
  13. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  14. 2026-10-21 11:46 UTCEG score recompute
  15. 2026-10-21 11:46 UTCVendor advisory
  16. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  17. 2026-10-20 13:09 UTCEG score recompute▲ 1.80
  18. 2026-10-20 13:09 UTCVendor advisory
  19. 2026-10-20 13:05 UTCNVD updateCVSS v3 → 9.3 · severity → CRITICAL
  20. 2026-10-19 19:17 UTCEG score recompute
  21. 2026-10-19 19:17 UTCVendor advisory
  22. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  23. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  24. 2026-10-18 03:20 UTCEG score recompute
  25. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  26. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  27. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  28. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  29. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  30. 2026-10-13 10:49 UTCEG score recompute
  31. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  32. 2026-10-12 15:45 UTCEG score recompute
  33. 2026-10-11 19:30 UTCEG score recompute
  34. 2026-10-11 16:46 UTCEG score recompute
  35. 2026-10-11 14:07 UTCEG score recompute
  36. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  37. 2026-10-11 05:41 UTCEG score recompute
  38. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  39. 2026-10-10 03:23 UTCEG score recompute
  40. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  41. 2026-10-09 01:04 UTCEG score recompute
  42. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  43. 2026-10-08 11:55 UTCEG score recompute
  44. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  45. 2026-10-06 20:05 UTCEG score recompute
  46. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  47. 2026-10-06 06:56 UTCEG score recompute
  48. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  49. 2026-10-05 04:32 UTCEG score recompute
  50. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  51. 2026-10-04 02:14 UTCEG score recompute
  52. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  53. 2026-10-02 23:58 UTCEG score recompute
  54. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  55. 2026-10-01 21:35 UTCEG score recompute
  56. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  57. 2026-09-30 19:18 UTCEG score recompute
  58. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  59. 2026-09-29 17:02 UTCEG score recompute
  60. 2026-09-29 03:54 UTCEG score recompute
  61. 2026-09-28 14:45 UTCEG score recompute
  62. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  63. 2026-09-27 23:13 UTCEG score recompute
  64. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  65. 2026-09-26 20:57 UTCEG score recompute
  66. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  67. 2026-09-25 18:39 UTCEG score recompute
  68. 2026-09-25 18:03 UTCEG score recompute
  69. 2026-09-25 17:37 UTCEG score recompute
  70. 2026-09-25 16:24 UTCEG score recomputeFirst assessed: 7.5 HIGH
  71. 2026-09-25 16:24 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-67237?
CVE-2026-67237 is a critical-severity vulnerability; its CVE record was published on September 25, 2026. 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…
When was the CVE record for CVE-2026-67237 published?
The CVE record for CVE-2026-67237 was published on September 25, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 20, 2026; the record at its source may have been updated since.
Is CVE-2026-67237 actively exploited?
CVE-2026-67237 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (39th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-67237?
CVE-2026-67237 has a CVSS v3 base score of 9.3 (NVD).
How do I remediate CVE-2026-67237?
A fix for CVE-2026-67237 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-67237 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-67237

Explore →

Is Your Infrastructure Affected by CVE-2026-67237?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs