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

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-11). 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.6.10-1ubuntu0.5+esm1) @ bionic2026-11-12ubuntu
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 15× in last 7d / 59× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 129 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 29 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

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