CVE-2026-54332

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.8% (56th 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 weekElevated

Also known asEUVD-2026-49894 (ENISA EUVD) · GHSA-g6v3-7xmc-w563 (GitHub Security Advisories)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).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

gopacket provides packet processing capabilities for Go. In version 1.6.0 and earlier, the sFlow ExtendedGatewayFlow decoder in layers/sflow.go reads an attacker-controlled 32-bit community count and AS path member count and sizes a slice allocation from those counts without bounding them against the bytes remaining in the datagram, so a 104-byte UDP datagram can drive an allocation of up to 16 GiB and cause an unauthenticated remote denial of service. This issue is fixed in version 1.6.1.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
65
EG Risk 65/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.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
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 public PoC (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.8%
EPSS %ILE
56th
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.8% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). 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: 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 public PoC (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.

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

July 28, 2026

Last Modified

August 5, 2026

Advisory Details (3)

Auto-updated Jul 28, 2026
Patch available. Sources: github, github_commit, github_release.
GitHub release Patch Available

v1.6.1

Patch available: gopacket/gopacket v1.6.1

https://github.com/gopacket/gopacket/releases/tag/v1.6.1
GitHub commit Patch Available

commit 76119086f593 (gopacket/gopacket)

Patch available: gopacket/gopacket v1.6.1 (contains commit 76119086f593)

https://github.com/gopacket/gopacket/commit/76119086f5936aacd7088bdf97d565501bb6c4cc
GitHub advisoryMentions a patch (unverified)

sFlow ExtendedGatewayFlow decoder: unbounded attacker-controlled allocation (104-byte UDP datagram -> up to 16 GiB make) -> unauthenticated remote DoS · Advisory · gopacket/gopacket · GitHub

https://github.com/gopacket/gopacket/security/advisories/GHSA-g6v3-7xmc-w563

Vendor Advisories for CVE-2026-54332(2)

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

Affected Packages

(8 across 5 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
golang-github-gopacket-gopacket1.0.0-1, 1.2.0-1, 1.2.0-2, 1.3.0-1, 1.3.0-2
  • every version on: no fix on record
—
gopacket1.1.19-3 ... 1.1.19-6.2 (6 versions)
  • every version on: no fix on record
—
Debian:13(2)
PackageVulnerable rangeFix by version rangeDependents
golang-github-gopacket-gopacket1.3.0-2
  • every version on: no fix on record
—
gopacket1.1.19-6.2
  • every version on: no fix on record
—
Debian:14(2)
PackageVulnerable rangeFix by version rangeDependents
golang-github-gopacket-gopacket1.3.0-2
  • every version on: no fix on record
—
gopacket1.1.19-6.2
  • every version on: no fix on record
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
gopacket1.1.19-1 ... 1.1.19-6.2 (8 versions)
  • every version on: no fix on record
—
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/gopacket/gopacket—
  • every version up to 1.6.1: fixed in 1.6.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.

Showing the most recent 100 of 215 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 115 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Same product

2 shown

Debian:11:gopacket · Go:github.com/gopacket/gopacket

Frequently asked(5)

What is CVE-2026-54332?
CVE-2026-54332 is a high-severity vulnerability; its CVE record was published on July 28, 2026. gopacket provides packet processing capabilities for Go. In version 1.6.0 and earlier, the sFlow ExtendedGatewayFlow decoder in layers/sflow.go reads an attacker-controlled 32-bit community count and AS path member count and sizes a slice allocation from those counts without bounding them against…
When was the CVE record for CVE-2026-54332 published?
The CVE record for CVE-2026-54332 was published on July 28, 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 August 5, 2026; the record at its source may have been updated since.
Is CVE-2026-54332 actively exploited?
CVE-2026-54332 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (56th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-54332?
CVE-2026-54332 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-54332?
A fix for CVE-2026-54332 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-54332 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-54332

Explore →

Is Your Infrastructure Affected by CVE-2026-54332?

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

Book a Demo →Browse All CVEs