<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Mon, 16 Nov 2026 18:43:39 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-396586</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-396586</link>
      <description>EUVD-2026-396586</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-396586</guid>
    </item>
    <item>
      <title>fkie_cve-2026-119299</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-119299</link>
      <description>&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-119299</guid>
    </item>
    <item>
      <title>GHSA-358w-w75h-x6rx — gopacket: SCTP chunk sub-decoder out-of-bounds panics on crafted segments</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-358w-w75h-x6rx</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/gopacket/gopacket&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;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&amp;#39;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&amp;#39;s per-packet panic recovery (`gopacket.DecodeOptions.SkipDecodeRecovery: true`); with the default API the same input degrades to a per-packet decode error.&lt;/p&gt;
&lt;p&gt;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`, &amp;#34;Multiple layer decoders panic …&amp;#34;, patched per advisory metadata in `v1.7.1`). The `v1.7.1` hardening commit `b772f56` (&amp;#34;layers:various: add protocol decoder length checks (#163)&amp;#34;) added generic bounds to the chunk dispatcher and `decodeSCTPChunk`, but left every chunk *sub-decoder* without a per-type minimum-length check. The advisory&amp;#39;s own description lists &amp;#34;SCTP chunk/parameter decoders (`sctp.go`)&amp;#34; among items &amp;#34;being confirmed; they should be remediated together with the above&amp;#34; - this report demonstrates that, at `v1.7.1` and `HEAD`, that remediation still does not exi…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/gopacket/gopacket&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;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&amp;#39;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&amp;#39;s per-packet panic recovery (`gopacket.DecodeOptions.SkipDecodeRecovery: true`); with the default API the same input degrades to a per-packet decode error.&lt;/p&gt;
&lt;p&gt;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`, &amp;#34;Multiple layer decoders panic …&amp;#34;, patched per advisory metadata in `v1.7.1`). The `v1.7.1` hardening commit `b772f56` (&amp;#34;layers:various: add protocol decoder length checks (#163)&amp;#34;) added generic bounds to the chunk dispatcher and `decodeSCTPChunk`, but left every chunk *sub-decoder* without a per-type minimum-length check. The advisory&amp;#39;s own description lists &amp;#34;SCTP chunk/parameter decoders (`sctp.go`)&amp;#34; among items &amp;#34;being confirmed; they should be remediated together with the above&amp;#34; - this report demonstrates that, at `v1.7.1` and `HEAD`, that remediation still does not exi…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-358w-w75h-x6rx</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-119299 — gopacket: SCTP chunk sub-decoder out-of-bounds panics on crafted segments</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-119299</link>
      <description>msrc_CVE-2026-119299</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-119299</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-119299</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-119299</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: golang-github-gopacket-gopacket, Ubuntu:26.10: golang-github-gopacket-gopacket, Ubuntu:26.04:LTS: golang-github-gopacket-gopacket&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: golang-github-gopacket-gopacket, Ubuntu:26.10: golang-github-gopacket-gopacket, Ubuntu:26.04:LTS: golang-github-gopacket-gopacket&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-119299</guid>
    </item>
  </channel>
</rss>
