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

> An attacker can cause a denial of service by sending a small UDP datagram that triggers excessive memory allocation in the sFlow decoder.

- **Severity:** Medium 6.9 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Jul 2026
- **Updated:** 28 Jul 2026
- **Also known as:** AZL-94323, CLEANSTART-2026-BH05638, DEBIAN-CVE-2026-54332, GHSA-g6v3-7xmc-w563, GO-2026-6122, MINI-2hgp-c865-m2g5, MINI-2qmq-vhmh-ph26, MINI-35cc-6x8j-w5mx, MINI-3v3x-3g75-fh57, MINI-44jh-fjgf-mjgf, MINI-59gr-4hp7-2j7v, MINI-5v89-9vqr-m22x, MINI-6vcx-h529-pfgx, MINI-7c89-ghm2-w225, MINI-c3gj-5v6q-r6hp, MINI-c84q-vfrf-9vqg, MINI-gvr3-xjh5-97q6, MINI-j654-v5hf-vc47, MINI-p9rr-724c-xgq5, MINI-pwx7-c8qf-h7v3, MINI-q43p-9m77-q5gv, MINI-q78c-4xrw-v9cx, MINI-qp8j-55w2-qqrh, MINI-qxqx-gmrm-6mw5, MINI-x3jp-rvxm-wqr6, UBUNTU-CVE-2026-54332

## What is CVE-2026-54332?

CVE-2026-54332 is a medium-severity denial of service vulnerability in gopacket, published on 28 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

## Which versions are affected by CVE-2026-54332?

3 open source packages ship an affected version, including github.com/gopacket/gopacket. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/gopacket/gopacket` | Go | All versions | 1.6.1 |
| `github.com/gopacket/gopacket` | Go | All versions | 1.6.1 |
| `github.com/gopacket/gopacket` | Go | All versions | 1.6.1 |

Products: Gopacket Gopacket.

## How do I fix CVE-2026-54332?

Upgrade github.com/gopacket/gopacket to 1.6.1 or later.

## Is CVE-2026-54332 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54332 exists.

## Other vulnerabilities in gopacket

- [CVE-2026-54345](https://insights.sbomify.com/CVE-2026-54345/): GoPacket's Diameter AVP decoder: uint32 underflow on vendor header size leads to unbounded ~4 GiB allocation (unauthenticated remote DoS) (medium 6.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-54332 and fix it if it is affected.

What it is: CVE-2026-54332 is a medium-severity denial of service vulnerability in gopacket, published on 28 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54332 exists.

Affected packages and fixed versions:
- github.com/gopacket/gopacket (Go): affected all versions; fixed in 1.6.1
- github.com/gopacket/gopacket (Go): affected all versions; fixed in 1.6.1
- github.com/gopacket/gopacket (Go): affected all versions; fixed in 1.6.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-54332/ (Markdown: https://insights.sbomify.com/CVE-2026-54332/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-54332
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-54332
- OSV: https://osv.dev/vulnerability/CVE-2026-54332

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-54332/
Summaries are generated and may contain mistakes; the official description above is the record.