CVE-2026-67239

MEDIUMNVD 5.45.4
EchelonGraph scoreMEDIUM confidence

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

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

5.4EG
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: 5.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

RabbitMQ is a messaging and streaming broker. From 3.13.0 until 3.13.18 and 4.0.23 and 4.1.14 and 4.2.9 and 4.3.3, Stored XSS via TLS peer-certificate DN in stream-management UI (sibling of V-11). lines 102/106/110 render peercertsubject / peercertissuer with raw <%= %> and no fmtstring(). RFC4514 backslash-escaping of is HTML-inert and bypassable (). Requires non-default config: a stream TLS listener with verifypeer and an attacker-obtainable trusted cert with a malicious Same as the connection.ejs finding, against operators viewing the stream-connection detail rabbitmqstream + rabbitmqstreammanagement enabled with a TLS listener using verifypeer Attacker can obtain a certificate signed by a CA the listener trusts, with attacker-chosen DN An operator views the. This issue is fixed in versions 3.13.18 and 4.0.23 and 4.1.14 and 4.2.9 and 4.3.3.

CVSS v3
5.4
EG Score
5.4MEDIUMmedium confidence
EG Risk
24
EG Risk 24/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)
Severity54% × 45%
Impact severity (EG Severity): CVSS 5.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 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.2%
EPSS %ILE
4th
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 (5.4): severity, escalated by confirmed exploitation. This CVE's 5.4 is its impact severity (EG Severity), not escalated.

EG Severity
5.4 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 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 16, 2026

Advisory Details (3)

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

RabbitMQ 4.3.3

Patch available: rabbitmq/rabbitmq-server v4.3.3

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

RabbitMQ 4.2.9

Patch available: rabbitmq/rabbitmq-server v4.2.9

https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.9
GitHub advisoryMentions a patch (unverified)

Stored XSS via TLS peer-certificate DN in stream-management UI (sibling of V-11) · Advisory · rabbitmq/rabbitmq-server · GitHub

https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-xm9p-57xv-vxwc

Vendor Advisories for CVE-2026-67239(2)

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.9.27-0ubuntu0.6) @ jammy2026-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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
rabbitmq-server3.10.8-1.1 ... 4.3.6-1 (29 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
rabbitmq-server4.0.5-10 ... 4.3.6-1 (19 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
rabbitmq-server4.0.5-10 ... 4.3.2-5 (16 versions)
  • every version up to 4.3.6-1: fixed in 4.3.6-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 7× in last 7d / 33× 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.

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

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

Frequently asked(5)

What is CVE-2026-67239?
CVE-2026-67239 is a medium-severity vulnerability; its CVE record was published on September 25, 2026. RabbitMQ is a messaging and streaming broker. From 3.13.0 until 3.13.18 and 4.0.23 and 4.1.14 and 4.2.9 and 4.3.3, Stored XSS via TLS peer-certificate DN in stream-management UI (sibling of V-11). lines 102/106/110 render peercertsubject / peercertissuer with raw <%= %> and no fmtstring(). RFC4514…
When was the CVE record for CVE-2026-67239 published?
The CVE record for CVE-2026-67239 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 16, 2026; the record at its source may have been updated since.
Is CVE-2026-67239 actively exploited?
CVE-2026-67239 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-67239?
CVE-2026-67239 has a CVSS v3 base score of 5.4 (NVD).
How do I remediate CVE-2026-67239?
A fix for CVE-2026-67239 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-67239 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-67239

Explore →

Is Your Infrastructure Affected by CVE-2026-67239?

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

Book a Demo →Browse All CVEs