Remote service crash via unbounded slice allocation
Published Jul 28, 2026 · Updated Jul 28, 2026
Resource exhaustion in gopacket 1.6.0 and earlier allows remote attackers to crash sFlow collectors via a crafted UDP datagram. The ExtendedGatewayFlow decoder in layers/sflow.go allocates uint32 slices from unbounded community and AS-path counts before checking the remaining bytes. Any host able to send UDP traffic to a collector that decodes sFlow with the library can terminate its process through memory exhaustion; no code execution or memory corruption is reported.
Summary
What happened
Resource exhaustion in gopacket 1.6.0 and earlier allows remote attackers to crash sFlow collectors via a crafted UDP datagram. The ExtendedGatewayFlow decoder in layers/sflow.go allocates uint32 slices from unbounded community and AS-path counts before checking the remaining bytes. Any host able to send UDP traffic to a collector that decodes sFlow with the library can terminate its process through memory exhaustion; no code execution or memory corruption is reported.
The record
- CVE
- CVE-2026-54332
- Published
- Jul 28, 2026
- Updated
- Jul 28, 2026
- Vendor
- Go standard library
- Product
- gopacket
- Classifications
- CWE-770, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 28, 2026CVE publishedPublication date reported by the CVE source.
- Jul 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.6.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GitHub advisory end-to-end sFlow collector PoCproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo