CVE-2026-54332

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.5%, top 59% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.5(medium)
EG Risk
38(Track)
EG Risk 38/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
41%
KEV
Not listed

Published

July 28, 2026

Last Modified

August 5, 2026

Advisory Details (3)

Auto-updated Jul 28, 2026
🔬 Proof of concept available. 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 Patch Available🟡 PoC Available

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

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 rangeFixed inDependents
golang-github-gopacket-gopacket1.0.0-1, 1.2.0-1, 1.2.0-2, 1.3.0-1, 1.3.0-2——
gopacket1.1.19-3 ... 1.1.19-6.2 (6 versions)——
Debian:13(2)
PackageVulnerable rangeFixed inDependents
golang-github-gopacket-gopacket1.3.0-2——
gopacket1.1.19-6.2——
Debian:14(2)
PackageVulnerable rangeFixed inDependents
golang-github-gopacket-gopacket1.3.0-2——
gopacket1.1.19-6.2——
Debian:11(1)
PackageVulnerable rangeFixed inDependents
gopacket1.1.19-1 ... 1.1.19-6.2 (8 versions)——
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/gopacket/gopacket—1.6.1—

Weakness Classification(1)

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 16× in last 7d / 85× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 130 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-54332?
CVE-2026-54332 is a high vulnerability 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 CVE-2026-54332 disclosed?
CVE-2026-54332 was first published in the National Vulnerability Database on July 28, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54332 actively exploited?
CVE-2026-54332 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 59.0% of all 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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54332, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs