CVE-2026-67236

MEDIUMNVD 6.56.5
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.2% (5th 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-87141 (ENISA EUVD)Source: ENISA EUVD

6.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 6.5Exploit: 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, a successful POST /login caused is_authorized/2 to set an auth cookie containing base64-encoded username:password credentials without HttpOnly, Secure, SameSite, or expiration protections. Because base64 is encoding rather than encryption, an attacker with same-origin cross-site scripting, an HTTP-readable network position, or local access to the browser cookie store could recover the actual login credentials; older browsers that treated an absent SameSite attribute as None also sent the cookie cross-site. This issue is fixed in versions 4.2.8 and 4.3.2.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
29
EG Risk 29/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)
Severity65% × 45%
Impact severity (EG Severity): CVSS 6.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 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 every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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.2%
EPSS %ILE
5th
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 (6.5): severity, escalated by confirmed exploitation. This CVE's 6.5 is its impact severity (EG Severity), not escalated.

EG Severity
6.5 MEDIUMCVSS-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.2% within 30 daysSource: FIRST EPSS. 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 every mission impact level.CISA BOD 26-04: 60 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 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). 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)60 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 partial (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 15, 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 edf1fbc7217a (rabbitmq/rabbitmq-server)

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

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

commit df9e7f4c0afd (rabbitmq/rabbitmq-server)

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

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

Plaintext username:password stored in an insecure cookie after successful POST /login · Advisory · rabbitmq/rabbitmq-server · GitHub

https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-88vh-gx85-p36m

Vendor Advisories for CVE-2026-67236(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.5.7-1ubuntu0.16.04.4+esm3) @ xenial2026-10-22ubuntu
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 8× in last 7d / 71× 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-01 16:35 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  2. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  3. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  4. 2026-10-30 07:55 UTCOSV refresh
  5. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  6. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  7. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  8. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  9. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  10. 2026-10-25 14:10 UTCEG score recompute
  11. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  12. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  13. 2026-10-22 19:35 UTCEG score recompute
  14. 2026-10-22 19:35 UTCVendor advisory
  15. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  16. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  17. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  18. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  19. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  20. 2026-10-18 03:20 UTCEG score recompute
  21. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  22. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  23. 2026-10-15 20:29 UTCEG score recompute▼ 1.70
  24. 2026-10-15 20:29 UTCVendor advisory
  25. 2026-10-15 20:28 UTCNVD updateCVSS v3 → 6.5 · severity → MEDIUM
Show 73 more
  1. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  2. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  3. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  4. 2026-10-13 10:49 UTCEG score recompute
  5. 2026-10-13 10:49 UTCVendor advisory
  6. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  7. 2026-10-12 15:45 UTCEG score recompute
  8. 2026-10-11 21:32 UTCVendor advisory
  9. 2026-10-11 19:30 UTCEG score recompute
  10. 2026-10-11 16:46 UTCEG score recompute
  11. 2026-10-11 14:07 UTCEG score recompute
  12. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  13. 2026-10-11 10:38 UTCVendor advisory
  14. 2026-10-10 23:45 UTCEG score recompute
  15. 2026-10-10 23:45 UTCVendor advisory
  16. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  17. 2026-10-10 12:56 UTCVendor advisory
  18. 2026-10-10 02:06 UTCEG score recompute
  19. 2026-10-10 02:06 UTCVendor advisory
  20. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  21. 2026-10-09 15:15 UTCVendor advisory
  22. 2026-10-09 03:47 UTCEG score recompute
  23. 2026-10-09 03:47 UTCVendor advisory
  24. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  25. 2026-10-08 16:56 UTCVendor advisory
  26. 2026-10-08 04:29 UTCEG score recompute
  27. 2026-10-08 04:29 UTCVendor advisory
  28. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  29. 2026-10-07 17:39 UTCVendor advisory
  30. 2026-10-07 05:20 UTCVendor advisory
  31. 2026-10-06 18:30 UTCEG score recompute
  32. 2026-10-06 18:30 UTCVendor advisory
  33. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  34. 2026-10-06 07:40 UTCVendor advisory
  35. 2026-10-05 20:51 UTCEG score recompute
  36. 2026-10-05 20:51 UTCVendor advisory
  37. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  38. 2026-10-05 10:02 UTCEG score recompute
  39. 2026-10-05 10:02 UTCVendor advisory
  40. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  41. 2026-10-04 23:12 UTCVendor advisory
  42. 2026-10-04 12:22 UTCVendor advisory
  43. 2026-10-04 01:32 UTCVendor advisory
  44. 2026-10-03 14:40 UTCEG score recompute
  45. 2026-10-03 14:40 UTCVendor advisory
  46. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  47. 2026-10-03 03:46 UTCEG score recompute
  48. 2026-10-03 03:46 UTCVendor advisory
  49. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  50. 2026-10-02 16:55 UTCVendor advisory
  51. 2026-10-02 06:06 UTCEG score recompute
  52. 2026-10-02 06:06 UTCVendor advisory
  53. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  54. 2026-10-01 19:15 UTCVendor advisory
  55. 2026-10-01 08:24 UTCVendor advisory
  56. 2026-09-30 21:34 UTCEG score recompute
  57. 2026-09-30 21:34 UTCVendor advisory
  58. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  59. 2026-09-30 10:39 UTCVendor advisory
  60. 2026-09-29 23:49 UTCEG score recompute
  61. 2026-09-29 23:49 UTCVendor advisory
  62. 2026-09-29 12:25 UTCVendor advisory
  63. 2026-09-29 01:35 UTCEG score recompute
  64. 2026-09-28 14:27 UTCEG score recompute
  65. 2026-09-28 13:57 UTCEG score recompute
  66. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  67. 2026-09-27 22:38 UTCEG score recompute
  68. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  69. 2026-09-27 00:58 UTCEG score recompute
  70. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  71. 2026-09-25 16:26 UTCEG score recompute
  72. 2026-09-25 16:07 UTCEG score recomputeFirst assessed: 8.2 HIGH
  73. 2026-09-25 16:04 UTCMITRE cvelistV5first tracked

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

Frequently asked(5)

What is CVE-2026-67236?
CVE-2026-67236 is a medium-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, a successful POST /login caused is_authorized/2 to set an auth cookie containing base64-encoded username:password credentials without HttpOnly, Secure, SameSite, or expiration protections. Because base64 is encoding…
When was the CVE record for CVE-2026-67236 published?
The CVE record for CVE-2026-67236 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 15, 2026; the record at its source may have been updated since.
Is CVE-2026-67236 actively exploited?
CVE-2026-67236 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-67236?
CVE-2026-67236 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-67236?
A fix for CVE-2026-67236 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-67236 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-67236

Explore →

Is Your Infrastructure Affected by CVE-2026-67236?

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

Book a Demo →Browse All CVEs