<?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>Sat, 03 Oct 2026 01:24:47 +0000</lastBuildDate>
    <item>
      <title>bdu:2023-05300</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2023-05300</link>
      <description>bdu:2023-05300</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2023-05300</guid>
    </item>
    <item>
      <title>EUVD-2026-216931</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-216931</link>
      <description>EUVD-2026-216931</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-216931</guid>
    </item>
    <item>
      <title>fkie_cve-2023-4809</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-4809</link>
      <description>&lt;p&gt;In pf packet processing with a &amp;#39;scrub fragment reassemble&amp;#39; rule, a packet containing multiple IPv6 fragment headers would be reassembled, and then immediately processed.  That is, a packet with multiple fragment extension headers would not be recognized as the correct ultimate payload. Instead a packet with multiple IPv6 fragment headers would unexpectedly be interpreted as a fragmented packet, rather than as whatever the real payload is.&lt;/p&gt;
&lt;p&gt;As a result, IPv6 fragments may bypass pf firewall rules written on the assumption all fragments have been reassembled and, as a result, be forwarded or processed by the host.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In pf packet processing with a &amp;#39;scrub fragment reassemble&amp;#39; rule, a packet containing multiple IPv6 fragment headers would be reassembled, and then immediately processed.  That is, a packet with multiple fragment extension headers would not be recognized as the correct ultimate payload. Instead a packet with multiple IPv6 fragment headers would unexpectedly be interpreted as a fragmented packet, rather than as whatever the real payload is.&lt;/p&gt;
&lt;p&gt;As a result, IPv6 fragments may bypass pf firewall rules written on the assumption all fragments have been reassembled and, as a result, be forwarded or processed by the host.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-4809</guid>
    </item>
    <item>
      <title>GHSA-g6hh-x63c-83gf</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-g6hh-x63c-83gf</link>
      <description>&lt;p&gt;In pf packet processing with a &amp;#39;scrub fragment reassemble&amp;#39; rule, a packet containing multiple IPv6 fragment headers would be reassembled, and then immediately processed.  That is, a packet with multiple fragment extension headers would not be recognized as the correct ultimate payload. Instead a packet with multiple IPv6 fragment headers would unexpectedly be interpreted as a fragmented packet, rather than as whatever the real payload is.&lt;/p&gt;
&lt;p&gt;As a result, IPv6 fragments may bypass pf firewall rules written on the assumption all fragments have been reassembled and, as a result, be forwarded or processed by the host.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In pf packet processing with a &amp;#39;scrub fragment reassemble&amp;#39; rule, a packet containing multiple IPv6 fragment headers would be reassembled, and then immediately processed.  That is, a packet with multiple fragment extension headers would not be recognized as the correct ultimate payload. Instead a packet with multiple IPv6 fragment headers would unexpectedly be interpreted as a fragmented packet, rather than as whatever the real payload is.&lt;/p&gt;
&lt;p&gt;As a result, IPv6 fragments may bypass pf firewall rules written on the assumption all fragments have been reassembled and, as a result, be forwarded or processed by the host.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-g6hh-x63c-83gf</guid>
    </item>
    <item>
      <title>gsd-2023-4809</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2023-4809</link>
      <description>gsd-2023-4809</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2023-4809</guid>
    </item>
    <item>
      <title>WID-SEC-W-2023-2281 — FreeBSD Project FreeBSD OS: Schwachstelle ermöglicht Umgehen von Sicherheitsvorkehrungen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2023-2281</link>
      <description>&lt;p&gt;Ein entfernter, anonymer Angreifer kann eine Schwachstelle in FreeBSD Project FreeBSD OS ausnutzen, um Sicherheitsvorkehrungen zu umgehen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, anonymer Angreifer kann eine Schwachstelle in FreeBSD Project FreeBSD OS ausnutzen, um Sicherheitsvorkehrungen zu umgehen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2023-2281</guid>
    </item>
  </channel>
</rss>
