Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.9amended

GoPacket's Diameter AVP decoder: uint32 underflow on vendor header size leads to unbounded ~4 GiB allocation (unauthenticated remote DoS)

CVE-2026-54345GHSA-6r28-9ppf-4hj5

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/gopacket/gopacket 1.6.1), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
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 · score source
EPSS
  • CVE-2026-54345: 0.79% estimated exploitation activity in the next 30 days; percentile 56.32 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary The Diameter AVP decoder in github.com/gopacket/gopacket computes dataLength := avp.Length - uint32(headerSize) without first ensuring avp.Length = headerSize. When the Vendor flag is set, headerSize is 12, but the only length guard upstream rejects avp.Length < 8. An AVP with the Vendor flag set and a 24-bit Length field of 8, 9, 10, or 11 therefore underflows the uint32 subtraction to ~4,294,967,292, which is passed straight to make([]byte, dataLength). A single 32-byte Diameter message forces a ~4 GiB allocation; a short burst of such messages exhausts memory and OOM-kills memory-constrained collectors. This is an unauthenticated remote denial of service (CWE-191 integer underflow - CWE-770 unbounded allocation). Root cause (file:line @ v1.6.0) layers/diameteravpdecoders.go, decodeDiameterAVP: For avp.Length in {8, 9, 10, 11} with the Vendor flag set: the avp.Length < 8 guard passes, paddedLength == avp.Length so only avp.Length bytes must be present, and dataLength =…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 4 · amended ·

    Amended from ghsa record GHSA-6r28-9ppf-4hj5

  2. Revision 3 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 2 · amended ·

    Amended from osv record GO-2026-6121

  4. Revision 1 · created ·

    Published from osv record GHSA-6r28-9ppf-4hj5

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-54345

Advisory: GoPacket's Diameter AVP decoder: uint32 underflow on vendor header size leads to unbounded ~4 GiB allocation (unauthenticated remote DoS)
IDs: CVE-2026-54345, GHSA-6r28-9ppf-4hj5
Record: https://patchnext.com/advisories/cve-2026-54345 (revision 4, source checked 26 Oct 2026, 15:27 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/gopacket/gopacket 1.6.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/gopacket/gopacket: affected <= 1.6.0; fixed in 1.6.1

## Suggested inspection (read-only)
- Go github.com/gopacket/gopacket: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/gopacket/gopacket.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-6r28-9ppf-4hj5 (OSV record GHSA-6r28-9ppf-4hj5 lists affected ranges: Go github.com/gopacket/gopacket >=0 <1.6.1 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6121 (OSV record GO-2026-6121 lists affected ranges: Go github.com/gopacket/gopacket >=0 <1.6.1 (fixed))
- Verified: https://github.com/advisories/GHSA-6r28-9ppf-4hj5 (GitHub-reviewed advisory GHSA-6r28-9ppf-4hj5 lists affected ranges: Go github.com/gopacket/gopacket >=0 <=1.6.0)

Commands are suggestions: review each one before running it.

Loading voting…