CVE-2026-67236

HIGHPre-NVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1% (1st 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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 8.2Exploit: 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
8.2
EG Score
8.2HIGHmedium confidence
EG Risk
37
EG Risk 37/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 computed
Severity82% × 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.1%
EPSS %ILE
1st
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, 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 Patch Available

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
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.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 27× in last 7d / 32× 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.

  1. 2026-10-04 12:22 UTCVendor advisory
  2. 2026-10-04 01:32 UTCVendor advisory
  3. 2026-10-03 14:40 UTCEG score recompute
  4. 2026-10-03 14:40 UTCVendor advisory
  5. 2026-10-03 14:26 UTCEPSS rescore
  6. 2026-10-03 03:46 UTCEG score recompute
  7. 2026-10-03 03:46 UTCVendor advisory
  8. 2026-10-02 17:56 UTCEPSS rescore
  9. 2026-10-02 16:55 UTCVendor advisory
  10. 2026-10-02 06:06 UTCEG score recompute
  11. 2026-10-02 06:06 UTCVendor advisory
  12. 2026-10-01 19:50 UTCEPSS rescore
  13. 2026-10-01 19:15 UTCVendor advisory
  14. 2026-10-01 08:24 UTCVendor advisory
  15. 2026-09-30 21:34 UTCEG score recompute
  16. 2026-09-30 21:34 UTCVendor advisory
  17. 2026-09-30 15:03 UTCEPSS rescore
  18. 2026-09-30 10:39 UTCVendor advisory
  19. 2026-09-29 23:49 UTCEG score recompute
  20. 2026-09-29 23:49 UTCVendor advisory
  21. 2026-09-29 12:25 UTCVendor advisory
  22. 2026-09-29 01:35 UTCEG score recompute
  23. 2026-09-28 14:27 UTCEG score recompute
  24. 2026-09-28 13:57 UTCEG score recompute
  25. 2026-09-28 13:52 UTCEPSS rescore
Show 7 more
  1. 2026-09-27 22:38 UTCEG score recompute
  2. 2026-09-27 13:48 UTCEPSS rescore
  3. 2026-09-27 00:58 UTCEG score recompute
  4. 2026-09-26 15:59 UTCEPSS rescore
  5. 2026-09-25 16:26 UTCEG score recompute
  6. 2026-09-25 16:07 UTCEG score recompute
  7. 2026-09-25 16:04 UTCMITRE cvelistV5first tracked

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-67236?
CVE-2026-67236 is a high vulnerability 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 CVE-2026-67236 disclosed?
CVE-2026-67236 was first published on September 25, 2026, with the most recent update on September 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-67236 actively exploited?
CVE-2026-67236 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-67236?
CVE-2026-67236 has a CVSS base score of 8.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
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.

Dependency Blast Radius

Explore the affected products and dependency analysis for 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