CVE-2026-119299

gopacket: SCTP chunk sub-decoder out-of-bounds panics on crafted segments

Published Oct 30, 2026 CVSS 3.1 · 5.9 Medium EPSS < 1% KEV · Not listed
Description
gopacket provides packet processing capabilities for Go. Prior to 1.7.2, the SCTP chunk chain in layers/sctp.go passes attacker-controlled declared lengths and counts to decodeSCTPInit, decodeSCTPShutdown, decodeSCTPError, decodeSCTPSack, and decodeSCTPParameter without checking that each chunk contains the fixed fields, parameter TLVs, gap acknowledgements, or duplicate TSNs those sub-decoders read. A crafted SCTP segment can therefore cause out-of-bounds or inverted slice panics; the panic can terminate applications that use gopacket.DecodeOptions.SkipDecodeRecovery, direct registered decoders, or DecodingLayerParser with IgnorePanic enabled, while the default recovery-enabled APIs convert it to a per-packet decode error. This is the SCTP sub-decoder residual named but not remediated by CVE-2026-65819, whose version 1.7.1 changes bounded the generic dispatcher but left these per-type reads and loops unchecked. The impact is availability only, with no data disclosure, modification, or allocation amplification. This issue is fixed in version 1.7.2.

Analysis

AI-generated

Technical impact

This vulnerability resides in gopacket’s SCTP packet parsing layer. Prior to version 1.7.2, the library hands attacker‑controlled chunk lengths and counts directly to several sub‑decoders without validating that each SCTP chunk contains the expected fields. The lack of bounds checks allows a crafted SCTP segment to trigger an out‑of‑bounds or inverted slice panic. When such a panic occurs, applications that have enabled SkipDecodeRecovery, IgnorePanic, or use direct registered decoders are terminated; otherwise the default recovery converts the panic into a per‑packet decode error but still consumes resources during processing. The flaw does not disclose data, modify information, or enable allocation amplification; it only interrupts packet‑processing services, resulting in a loss of availability.

Affected Systems

The gopacket library, used by Go developers for packet capture, analysis, and network protocol handling, is affected. Any application that imports gopacket prior to release 1.7.2 is vulnerable. The fix is implemented in gopacket v1.7.2 and later, so upgrade to that or newer to remediate.

Risk and Exploitability

The CVSS score of 5.9 indicates medium severity. EPSS data is not available, and the vulnerability is not listed in CISA’s KEV catalogue. Attackers can exploit the flaw by sending a malicious SCTP packet to any host that parses SCTP frames with gopacket. Based on the description, the likely attack vector is forged SCTP traffic over a network interface. If the target application has SkipDecodeRecovery or IgnorePanic enabled, the panic will crash the process; otherwise the library will report a decode error for the offending packet. In both cases the vulnerability causes a denial of service at the application or service level.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade gopacket to version 1.7.2 or later
  • Disable SkipDecodeRecovery and IgnorePanic when processing external SCTP traffic, as these options make the panic fatal
  • Validate or sanitize SCTP packets before passing them to gopacket in environments that receive untrusted input

Generated by OpenCVE AI on October 30, 2026 at 17:38 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-358w-w75h-x6rx gopacket: SCTP chunk sub-decoder out-of-bounds panics on crafted segments
History
Type Values Removed Values Added
First Time appeared Gopacket
Gopacket gopacket
Vendors & Products Gopacket
Gopacket gopacket
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description gopacket provides packet processing capabilities for Go. Prior to 1.7.2, the SCTP chunk chain in layers/sctp.go passes attacker-controlled declared lengths and counts to decodeSCTPInit, decodeSCTPShutdown, decodeSCTPError, decodeSCTPSack, and decodeSCTPParameter without checking that each chunk contains the fixed fields, parameter TLVs, gap acknowledgements, or duplicate TSNs those sub-decoders read. A crafted SCTP segment can therefore cause out-of-bounds or inverted slice panics; the panic can terminate applications that use gopacket.DecodeOptions.SkipDecodeRecovery, direct registered decoders, or DecodingLayerParser with IgnorePanic enabled, while the default recovery-enabled APIs convert it to a per-packet decode error. This is the SCTP sub-decoder residual named but not remediated by CVE-2026-65819, whose version 1.7.1 changes bounded the generic dispatcher but left these per-type reads and loops unchecked. The impact is availability only, with no data disclosure, modification, or allocation amplification. This issue is fixed in version 1.7.2.
Title gopacket: SCTP chunk sub-decoder out-of-bounds panics on crafted segments
Weaknesses CWE-125
CWE-129
References
Metrics cvssV3_1

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

Weaknesses
  • CWE-125

    Out-of-bounds Read

  • CWE-129

    Improper Validation of Array Index

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Oct 30, 2026, 4:54 PM
Reserved
Oct 29, 2026, 6:50 PM
Status
Awaiting Analysis
Published
Oct 30, 2026, 5:17 PM
Modified
Oct 30, 2026, 7:37 PM
Severity
Moderate
Public date
Oct 30, 2026, 4:23 PM