CVE-2026-67414

MEDIUMPre-NVD 6.06.0
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 6.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6% (50th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this weekElevated

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

6.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 6.0Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

RabbitMQ is a messaging and streaming broker. From 4.0.0 until 4.0.24, 4.1.15, 4.2.10, and 4.3.4, deps/amqp10_common/src/amqp10_binary_parser.erl materializes each element of AMQP 1.0 arrays whose shared constructor has zero width, while limiting only the number of elements in each array and not the aggregate arrays in a frame. After completing SASL authentication, a low-privilege client can send an ordinary frame containing many individually permitted arrays, causing a small frame to expand into a very large reader-process heap before later frame validation or authorization. Because deps/rabbit/src/rabbit_amqp_reader.erl clears the pre-authentication max_heap_size guard after login, repeated or concurrent frames can trigger the node-wide memory alarm, block publishers, or exhaust broker memory. This issue is fixed in versions 4.0.24, 4.1.15, 4.2.10, and 4.3.4.

CVSS v3
6.0
EG Score
6.0MEDIUMmedium confidence
EG Risk
43
EG Risk 43/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)
Severity60% × 45%
Impact severity (EG Severity): CVSS 6.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
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 public PoC (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.6%
EPSS %ILE
50th
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.0): severity, escalated by confirmed exploitation. This CVE's 6.0 is its impact severity (EG Severity), not escalated.

EG Severity
6.0 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.6% 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: 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 low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (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

October 14, 2026

Last Modified

October 29, 2026

Advisory Details (3)

Auto-updated Oct 14, 2026
🔬 Proof of concept available. Patch available. Sources: github_release, github, github_commit.
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

RabbitMQ AMQP 1.0 parser: amplification memory-exhaustion DoS via zero-width array aggregation · Advisory · rabbitmq/rabbitmq-server · GitHub

https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-w6mq-4qpx-v7mh
GitHub release Patch Available

RabbitMQ 4.3.4

Patch available: rabbitmq/rabbitmq-server v4.3.4

https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.4
GitHub commit

commit 3f0f67dfb7c4 (rabbitmq/rabbitmq-server)

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

https://github.com/rabbitmq/rabbitmq-server/commit/3f0f67dfb7c4390e3cbfa25ab3ee19dcb0845bd4

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrabbitmq-server4-3-main-4.3.6-1.1.hum12026-10-14redhat

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(2)

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 13× in last 7d / 32× 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.6% · 50th percentile
  2. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  3. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  4. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  5. 2026-10-29 15:35 UTCEG score recompute
  6. 2026-10-29 15:35 UTCVendor advisory
  7. 2026-10-29 14:25 UTCEG score recompute
  8. 2026-10-29 14:25 UTCVendor advisory
  9. 2026-10-29 14:24 UTCEG score recompute
  10. 2026-10-29 14:24 UTCVendor advisory
  11. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  12. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  13. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  14. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  15. 2026-10-25 14:10 UTCEG score recompute
  16. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  17. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  18. 2026-10-22 19:34 UTCEG score recompute
  19. 2026-10-22 19:34 UTCVendor advisory
  20. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  21. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  22. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  23. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  24. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  25. 2026-10-18 03:20 UTCEG score recompute
Show 7 more
  1. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  2. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  3. 2026-10-16 16:14 UTCEG score recompute
  4. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  5. 2026-10-14 18:30 UTCEG score recompute
  6. 2026-10-14 16:11 UTCEG score recomputeFirst assessed: 6.0 MEDIUM
  7. 2026-10-14 16:09 UTCMITRE cvelistV5first tracked

Related CVEs(same vendor + same CWE)

Same vendor

2 shown

redhat:RHSA-2026:82703

Frequently asked(5)

What is CVE-2026-67414?
CVE-2026-67414 is a medium-severity vulnerability; its CVE record was published on October 14, 2026. RabbitMQ is a messaging and streaming broker. From 4.0.0 until 4.0.24, 4.1.15, 4.2.10, and 4.3.4, deps/amqp10_common/src/amqp10_binary_parser.erl materializes each element of AMQP 1.0 arrays whose shared constructor has zero width, while limiting only the number of elements in each array and not…
When was the CVE record for CVE-2026-67414 published?
The CVE record for CVE-2026-67414 was published on October 14, 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 29, 2026; the record at its source may have been updated since.
Is CVE-2026-67414 actively exploited?
CVE-2026-67414 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (50th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-67414?
CVE-2026-67414 has a CVSS base score of 6.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-67414?
A fix for CVE-2026-67414 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-67414

Explore →

Is Your Infrastructure Affected by CVE-2026-67414?

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

Book a Demo →Browse All CVEs