CVE-2026-66079

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.3% (24th 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 — 3 sources updated this week

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

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.5Exploit: 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, and 4.2.6, parse_array_primitive/2 for constructor 0x45 (list0) returns an element with byte-width B = 0. The enclosing array32 parser at line 148 reads a 4-byte Count from the wire and loops Count times consuming B bytes each , with B = 0, no input is consumed and the loop builds a list of Count empty elements bounded only by the 32-bit field. The SASL-mechanisms / SASL-init frame is parsed by amqp10_framing:decode_bin/1 from rabbit_amqp_reader.erl:412 before authentication completes. The pre-auth incoming_max_frame_size (default 8192 bytes) caps the frame, not the Count field, so a 19-byte payload with Count = 0xFFFFFFFF is accepted. No max_heap_size is set on the reader process. An unauthenticated network attacker can crash any RabbitMQ node that has the AMQP 1.0 listener enabled (default port 5672) by sending a single ~19-byte frame. The reader process attempts to build a list of ~4 billion empty elements, exhausting heap memory and terminating the Erlang VM. All tenants and protocols on the node lose service. Preconditions include Network reachability to the AMQP listener (port 5672, enabled by default) No authentication required. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/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)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.3%
EPSS %ILE
24th
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 (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-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.3% 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 low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days 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; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (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 (2)

Auto-updated Sep 23, 2026
Patch available. Sources: github, github_release.
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
GitHub advisoryMentions a patch (unverified)

Pre-auth AMQP 1.0 array32 zero-width element DoS · Advisory · rabbitmq/rabbitmq-server · GitHub

https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-c66h-hf5j-8jf9

Vendor Advisories for CVE-2026-66079(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.5.7-1ubuntu0.16.04.4+esm3) @ xenial2026-10-29ubuntu
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-1 (9 versions)
  • every version up to 4.3.0-2: fixed in 4.3.0-2
—

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 9× in last 7d / 70× 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.

Showing the most recent 100 of 106 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 6 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  2. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  3. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  4. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  5. 2026-10-29 02:56 UTCEG score recompute
  6. 2026-10-29 02:56 UTCVendor advisory
  7. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  8. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  9. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  10. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  11. 2026-10-25 14:11 UTCEG score recompute
  12. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  13. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  14. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  15. 2026-10-22 11:32 UTCEG score recompute
  16. 2026-10-22 11:32 UTCVendor advisory
  17. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  18. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  19. 2026-10-19 20:47 UTCEG score recompute▼ 0.70
  20. 2026-10-19 20:47 UTCVendor advisory
  21. 2026-10-19 20:45 UTCNVD updateCVSS v3 → 7.5
  22. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  23. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  24. 2026-10-18 03:21 UTCEG score recompute
  25. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
Show 75 more
  1. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  2. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  3. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  4. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  5. 2026-10-13 10:59 UTCEG score recompute
  6. 2026-10-13 10:59 UTCVendor advisory
  7. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  8. 2026-10-12 15:46 UTCEG score recompute
  9. 2026-10-11 21:32 UTCVendor advisory
  10. 2026-10-11 19:31 UTCEG score recompute
  11. 2026-10-11 16:46 UTCEG score recompute
  12. 2026-10-11 14:07 UTCEG score recompute
  13. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  14. 2026-10-11 09:01 UTCVendor advisory
  15. 2026-10-10 20:48 UTCEG score recompute
  16. 2026-10-10 20:48 UTCVendor advisory
  17. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  18. 2026-10-10 08:39 UTCVendor advisory
  19. 2026-10-09 20:29 UTCEG score recompute
  20. 2026-10-09 20:29 UTCVendor advisory
  21. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  22. 2026-10-09 08:19 UTCVendor advisory
  23. 2026-10-08 20:09 UTCEG score recompute
  24. 2026-10-08 20:09 UTCVendor advisory
  25. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  26. 2026-10-08 07:40 UTCEG score recompute
  27. 2026-10-08 07:40 UTCVendor advisory
  28. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  29. 2026-10-07 19:31 UTCVendor advisory
  30. 2026-10-07 07:18 UTCVendor advisory
  31. 2026-10-06 19:08 UTCEG score recompute
  32. 2026-10-06 19:08 UTCVendor advisory
  33. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  34. 2026-10-06 06:58 UTCVendor advisory
  35. 2026-10-05 18:24 UTCEG score recompute
  36. 2026-10-05 18:24 UTCVendor advisory
  37. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  38. 2026-10-05 06:15 UTCEG score recompute
  39. 2026-10-05 06:15 UTCVendor advisory
  40. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  41. 2026-10-04 18:05 UTCVendor advisory
  42. 2026-10-04 05:55 UTCVendor advisory
  43. 2026-10-03 17:46 UTCEG score recompute
  44. 2026-10-03 17:46 UTCVendor advisory
  45. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  46. 2026-10-03 05:37 UTCEG score recompute
  47. 2026-10-03 05:37 UTCVendor advisory
  48. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  49. 2026-10-02 17:27 UTCVendor advisory
  50. 2026-10-02 05:14 UTCEG score recompute
  51. 2026-10-02 05:14 UTCVendor advisory
  52. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  53. 2026-10-01 17:03 UTCVendor advisory
  54. 2026-10-01 04:54 UTCVendor advisory
  55. 2026-09-30 16:38 UTCEG score recompute
  56. 2026-09-30 16:38 UTCVendor advisory
  57. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  58. 2026-09-30 03:59 UTCVendor advisory
  59. 2026-09-29 15:50 UTCEG score recompute
  60. 2026-09-29 15:50 UTCVendor advisory
  61. 2026-09-29 03:33 UTCEG score recompute
  62. 2026-09-29 03:33 UTCVendor advisory
  63. 2026-09-29 02:36 UTCEG score recompute
  64. 2026-09-29 02:36 UTCVendor advisory
  65. 2026-09-28 16:25 UTCEG score recompute
  66. 2026-09-28 16:25 UTCVendor advisory
  67. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  68. 2026-09-28 04:15 UTCVendor advisory
  69. 2026-09-27 16:05 UTCEG score recompute
  70. 2026-09-27 16:05 UTCVendor advisory
  71. 2026-09-27 03:56 UTCEG score recompute
  72. 2026-09-27 03:56 UTCVendor advisory
  73. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  74. 2026-09-26 15:46 UTCVendor advisory
  75. 2026-09-26 03:37 UTCEG score recompute

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

Frequently asked(5)

What is CVE-2026-66079?
CVE-2026-66079 is a high-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, and 4.2.6, parse_array_primitive/2 for constructor 0x45 (list0) returns an element with byte-width B = 0. The enclosing array32 parser at line 148 reads a 4-byte Count from the wire and loops Count times…
When was the CVE record for CVE-2026-66079 published?
The CVE record for CVE-2026-66079 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-66079 actively exploited?
CVE-2026-66079 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (24th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-66079?
CVE-2026-66079 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-66079?
A fix for CVE-2026-66079 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-66079 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-66079

Explore →

Is Your Infrastructure Affected by CVE-2026-66079?

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

Book a Demo →Browse All CVEs