gopacket: SCTP chunk sub-decoder out-of-bounds panics on crafted segments
Affects gopacket through v1.7.1 and the master branch at the time of the report. The fix is in gopacket 1.7.2. No vendor severity rating is given, so the CVSS score of 5.9 (medium) is the only rating.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 1.7.2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: poc
- Automatable: no
- Technical impact: partial
Summary
The gopacket Go library's SCTP packet decoding is affected, so applications that parse SCTP traffic with it can be crashed by a specially crafted SCTP packet. The impact is a denial of service (availability only) that can terminate the application when panic recovery is disabled.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original 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.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- gopacket gopacket
fixed in 1.7.2
References 3
GitHub · gopacket/gopacket
Questions about CVE-2026-119299
What does this mean?
The SCTP chunk sub-decoder reads past the end of its buffer when it parses crafted SCTP segments, which makes gopacket panic while decoding.Source: github.com
Am I affected, and how do I check?
Every released version through v1.7.1 and the master branch at the time of the report are affected. To check a project, look at the gopacket version it pins in go.mod, or the commit if it builds from master.Source: github.com
What should I do about it?
Upgrade to gopacket 1.7.2. Until then, keep panic recovery enabled by leaving SkipDecodeRecovery unset and IgnorePanic set to false.Source: github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data