CVE-2026-65819

gopacket: Multiple layer decoders panic on crafted packets (out-of-bounds/underflow) enabling unauthenticated remote DoS via DecodingLayerParser

Published Aug 7, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
Description
gopacket provides packet processing capabilities for Go. Through version 1.7.0, multiple layer decoders use attacker-controlled lengths, counts, or offsets before validating them against packet buffers, allowing a crafted packet decoded through DecodingLayerParser or DecodeFromBytes to trigger an unrecovered panic and remotely deny service. A patch commit is available at 210f25f.

Analysis

AI-generated

Technical impact

Multiple layer decoders in gopacket use attacker-controlled lengths, counts, or offsets before validating against packet buffers. A crafted packet decoded through DecodingLayerParser or DecodeFromBytes can trigger an unrecovered panic, effectively crashing the process that uses the library. The vulnerability is a classic out‑of‑bounds read (CWE‑125) that results in denial of service (CWE‑400). It allows an unauthenticated attacker to stop the target from processing any further packets, compromising availability.

Affected Systems

The vulnerability affects the gopacket library for the Go programming language. All applications or services that depend on gopacket versions up to and including 1.7.0 are susceptible. No later versions have been confirmed; a patch was merged in commit 210f25f and released in v1.7.1.

Risk and Exploitability

The CVSS score of 7.5 indicates a high severity, and the EPSS score of < 1% suggests a very low exploitation probability, though it is not zero. The vulnerability is not listed in the CISA KEV catalog. It is likely to be exploited by sending a maliciously crafted network packet to any service or library consumer that decodes packets using the affected decoder. The vulnerability does not require authentication, so any remote host that can deliver the packet is a potential attacker.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the gopacket library to version 1.7.1 or later to apply the patch that validates lengths and offsets before decoding.
  • If an upgrade is not immediately possible, implement defensive checks in the application code to verify packet lengths, counts, and offsets before passing data to DecodingLayerParser or DecodeFromBytes.
  • Add monitoring or graceful recovery around the decoding calls to catch panics and prevent a full service crash, ensuring that the process can recover or restart automatically.

Generated by OpenCVE AI on August 11, 2026 at 02:06 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Gopacket
Gopacket gopacket
Vendors & Products Gopacket
Gopacket gopacket
Type Values Removed Values Added
Description gopacket provides packet processing capabilities for Go. Through version 1.7.0, multiple layer decoders use attacker-controlled lengths, counts, or offsets before validating them against packet buffers, allowing a crafted packet decoded through DecodingLayerParser or DecodeFromBytes to trigger an unrecovered panic and remotely deny service. A patch commit is available at 210f25f.
Title gopacket: Multiple layer decoders panic on crafted packets (out-of-bounds/underflow) enabling unauthenticated remote DoS via DecodingLayerParser
Weaknesses CWE-125
CWE-400
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}

Weaknesses
  • CWE-125

    Out-of-bounds Read

  • CWE-400

    Uncontrolled Resource Consumption

  • CWE-805

    Buffer Access with Incorrect Length Value

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Aug 11, 2026, 1:07 AM
Reserved
Jul 22, 2026, 11:16 PM
Status
Deferred
Published
Aug 7, 2026, 8:16 PM
Modified
Sep 9, 2026, 9:02 PM
Severity
Important
Public date
Aug 7, 2026, 7:19 PM