Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-g6v3-7xmc-w563

GoPacket's sFlow ExtendedGatewayFlow decoder: unbounded attacker-controlled allocation (104-byte UDP datagram -> up to 16 GiB make) -> unauthenticated remote DoS

CVSS 6.9 MediumEPSS 0.0079 · 56th percentile

Published by the GitHub Advisory Database at 28 Jul 2026, 16:17 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/gopacket/gopacketGo<1.6.11.6.1
Identifiers
GHSA-g6v3-7xmc-w563 · CVE-2026-54332 · GO-2026-6122
Weakness (CWE)
CWE-770
Tags
Published
28 Jul 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

GoPacket versions before 1.6.1 of github.com/gopacket/gopacket are vulnerable. The sFlow ExtendedGatewayFlow record decoder allocates memory based on an attacker-supplied count field without checking it against the datagram size, so a single small UDP datagram can force a very large allocation. An unauthenticated remote attacker who can send UDP packets to a service parsing sFlow with gopacket can crash that process through memory exhaustion. Upgrade to version 1.6.1 or later.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
6.9 Medium 4.0 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0079, the 56th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:14 UTC First seen by agentprime
  2. 31 Oct 2026, 14:14 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.