<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-16T18:43:40.302239+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-396586</id>
    <title>EUVD-2026-396586</title>
    <updated>2026-11-16T18:43:40.305565+00:00</updated>
    <content>EUVD-2026-396586</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-396586"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-119299</id>
    <title>fkie_cve-2026-119299</title>
    <updated>2026-11-16T18:43:40.305598+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-119299"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-358w-w75h-x6rx</id>
    <title>GHSA-358w-w75h-x6rx — gopacket: SCTP chunk sub-decoder out-of-bounds panics on crafted segments</title>
    <updated>2026-11-16T18:43:40.305633+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/gopacket/gopacket</p>
<p>## Summary</p>
<p>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.</p>
<p>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`). The `v1.7.1` hardening commit `b772f56` ("layers:various: add protocol decoder length checks (#163)") added generic bounds to the chunk dispatcher and `decodeSCTPChunk`, but left every chunk *sub-decoder* without a per-type minimum-length check. The advisory's own description lists "SCTP chunk/parameter decoders (`sctp.go`)" among items "being confirmed; they should be remediated together with the above" - this report demonstrates that, at `v1.7.1` and `HEAD`, that remediation still does not exi…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-358w-w75h-x6rx"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/msrc_cve-2026-119299</id>
    <title>msrc_CVE-2026-119299 — gopacket: SCTP chunk sub-decoder out-of-bounds panics on crafted segments</title>
    <updated>2026-11-16T18:43:40.305748+00:00</updated>
    <content>msrc_CVE-2026-119299</content>
    <link href="https://cve.radiocsirt.org/vuln/msrc_cve-2026-119299"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-119299</id>
    <title>UBUNTU-CVE-2026-119299</title>
    <updated>2026-11-16T18:43:40.305767+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:24.04:LTS: golang-github-gopacket-gopacket, Ubuntu:26.10: golang-github-gopacket-gopacket, Ubuntu:26.04:LTS: golang-github-gopacket-gopacket</p>
<p>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.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-119299"/>
  </entry>
</feed>
