Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.9amended

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

CVE-2026-119299GHSA-358w-w75h-x6rx

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/gopacket/gopacket 1.7.2), 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
5.9 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
  • CVE-2026-119299: 0.47% estimated exploitation activity in the next 30 days; percentile 41.01 (FIRST EPSS, 2026-11-10). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary gopacket decodes SCTP (IP protocol 132) by walking the chunk chain through per-chunk-type decoder functions (`decodeSCTPInit`, `decodeSCTPShutdown`, `decodeSCTPError`, `decodeSCTPSack`, in `layers/sctp.go`). Each of these reads fixed-size header fields and runs count-driven loops without validating the chunk's declared length against the minimums those reads require. A single crafted SCTP segment causes a runtime panic (out-of-bounds slice read, or inverted slice from unsigned length arithmetic) on any decode path that does not install gopacket's per-packet panic recovery (`gopacket.DecodeOptions.SkipDecodeRecovery: true`); with the default API the same input degrades to a per-packet decode error. The defect is present in every released version through `v1.7.1` and at current `master` (18c5805). It is the SCTP component named - but not remediated - in CVE-2026-65819 (`GHSA-8mcr-459q-5mx2`, "Multiple layer decoders panic …", patched per advisory metadata in `v1.7.1`).…

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

    Amended from osv record GHSA-358w-w75h-x6rx

  2. Revision 1 · created ·

    Published from ghsa record GHSA-358w-w75h-x6rx

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-119299

Advisory: gopacket: SCTP chunk sub-decoder out-of-bounds panics on crafted segments
IDs: CVE-2026-119299, GHSA-358w-w75h-x6rx
Record: https://patchnext.com/advisories/cve-2026-119299 (revision 2, source checked 11 Nov 2026, 07:20 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.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.7.2. A vendor fix does not mean a deployment is fixed.

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

## 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://github.com/advisories/GHSA-358w-w75h-x6rx (GitHub-reviewed advisory GHSA-358w-w75h-x6rx lists affected ranges: Go github.com/gopacket/gopacket >=0 <=1.7.1)
- Verified: https://osv.dev/vulnerability/GHSA-358w-w75h-x6rx (OSV record GHSA-358w-w75h-x6rx lists affected ranges: Go github.com/gopacket/gopacket >=0 <1.7.2 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…