CVE-2026-67224

MEDIUMNVD 4.94.9
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 4.9 under NVD CVSS v3. EPSS exploit probability: 0.4% (29th 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 — 4 sources updated this week

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

4.9EG
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.4%CVSS: 4.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

RabbitMQ is a messaging and streaming broker. Prior to versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.1, The trace consumer constructs the output path as filename:join(TraceDir, Name ++ ".log") where Name comes from PUT /api/traces/:vhost/:name. No safe_relative_path / traversal check is applied on the write side, while the read side (rabbit_tracing_files.erl) does call rabbit_misc:safe_relative_path/1 , proving the omission is an oversight, not design. The .log suffix is forced and the endpoint requires administrator. A user with the administrator tag can write a .log-suffixed file to an arbitrary filesystem path writable by the rabbitmq user via the tracing plugin's name parameter, e.g. /etc/cron.d/x.log (if writable) or overwrite existing .log files outside the trace directory. Preconditions include rabbitmq_tracing plugin enabled administrator tag Target path writable by rabbitmq OS user. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.1.

CVSS v3
4.9
EG Score
4.9MEDIUMmedium confidence
EG Risk
22
EG Risk 22/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)
Severity49% × 45%
Impact severity (EG Severity): CVSS 4.9 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 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.4%
EPSS %ILE
29th
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 (4.9): severity, escalated by confirmed exploitation. This CVE's 4.9 is its impact severity (EG Severity), not escalated.

EG Severity
4.9 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.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-28). 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 23, 2026

Last Modified

October 19, 2026

Advisory Details (3)

Auto-updated Oct 19, 2026
Patch available. Sources: github_release, github.
GitHub advisoryMentions a patch (unverified)

Admin path-traversal write via trace name · Advisory · rabbitmq/rabbitmq-server · GitHub

https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-h7cq-qrr8-7vgc
GitHub release Patch Available

RabbitMQ 4.3.1

Patch available: rabbitmq/rabbitmq-server v4.3.1

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

RabbitMQ 4.2.6

Patch available: rabbitmq/rabbitmq-server v4.2.6

https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.6

Vendor Advisories for CVE-2026-67224(2)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / 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.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
rabbitmq-server3.10.8-1.1 ... 4.3.2-5 (28 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
rabbitmq-server4.0.5-10 ... 4.3.2-5 (18 versions)
  • every version on: no fix on record
—
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.

Data Freshness Timeline

(refreshed 10× in last 7d / 48× 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.4% · 29th percentile
  2. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  3. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  4. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  5. 2026-10-29 14:43 UTCEG score recompute
  6. 2026-10-29 14:43 UTCVendor advisory
  7. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  8. 2026-10-28 12:55 UTCOSV refresh
  9. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  10. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  11. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  12. 2026-10-25 14:10 UTCEG score recompute
  13. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  14. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  15. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  16. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  17. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  18. 2026-10-19 20:49 UTCEG score recompute▲ 2.80
  19. 2026-10-19 20:49 UTCVendor advisory
  20. 2026-10-19 20:45 UTCNVD updateCVSS v3 → 4.9 · severity → MEDIUM
  21. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  22. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  23. 2026-10-18 03:20 UTCEG score recompute
  24. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  25. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.4% · 30th percentile
Show 39 more
  1. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  2. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  3. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  4. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  5. 2026-10-12 15:45 UTCEG score recompute
  6. 2026-10-11 19:30 UTCEG score recompute
  7. 2026-10-11 16:46 UTCEG score recompute
  8. 2026-10-11 14:07 UTCEG score recompute
  9. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  10. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  11. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  12. 2026-10-09 12:40 UTCEG score recompute
  13. 2026-10-09 12:40 UTCVendor advisory
  14. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  15. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  16. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  17. 2026-10-06 12:31 UTCEG score recompute
  18. 2026-10-06 12:31 UTCVendor advisory
  19. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  20. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  21. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  22. 2026-10-03 13:34 UTCEG score recompute
  23. 2026-10-03 13:34 UTCVendor advisory
  24. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  25. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  26. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  27. 2026-09-30 14:37 UTCEG score recompute
  28. 2026-09-30 14:37 UTCVendor advisory
  29. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  30. 2026-09-27 15:34 UTCEG score recompute
  31. 2026-09-27 15:34 UTCVendor advisory
  32. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  33. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  34. 2026-09-24 16:37 UTCEG score recompute
  35. 2026-09-24 15:32 UTCEG score recompute
  36. 2026-09-24 15:08 UTCEG score recompute
  37. 2026-09-23 21:23 UTCEG score recompute
  38. 2026-09-23 20:24 UTCEG score recomputeFirst assessed: 2.1 LOW
  39. 2026-09-23 20:23 UTCMITRE cvelistV5first tracked

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

Frequently asked(5)

What is CVE-2026-67224?
CVE-2026-67224 is a medium-severity vulnerability; its CVE record was published on September 23, 2026. RabbitMQ is a messaging and streaming broker. Prior to versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.1, The trace consumer constructs the output path as filename:join(TraceDir, Name ++ ".log") where Name comes from PUT /api/traces/:vhost/:name. No safe_relative_path / traversal check is applied…
When was the CVE record for CVE-2026-67224 published?
The CVE record for CVE-2026-67224 was published on September 23, 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 19, 2026; the record at its source may have been updated since.
Is CVE-2026-67224 actively exploited?
CVE-2026-67224 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (29th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-67224?
CVE-2026-67224 has a CVSS v3 base score of 4.9 (NVD).
How do I remediate CVE-2026-67224?
A fix for CVE-2026-67224 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-67224 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-67224

Explore →

Is Your Infrastructure Affected by CVE-2026-67224?

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

Book a Demo →Browse All CVEs