<?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>Wed, 07 Oct 2026 18:30:13 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-292744</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-292744</link>
      <description>EUVD-2026-292744</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-292744</guid>
    </item>
    <item>
      <title>fkie_cve-2026-34063</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-34063</link>
      <description>&lt;p&gt;Nimiq&amp;#39;s network-libp2p is a Nimiq network implementation based on libp2p. Prior to version 1.3.0, `network-libp2p` discovery uses a libp2p `ConnectionHandler` state machine. the handler assumes there is at most one inbound and one outbound discovery substream per connection. if a remote peer opens/negotiate the discovery protocol substream a second time on the same connection, the handler hits a `panic!(\&amp;#34;Inbound already connected\&amp;#34;)` / `panic!(\&amp;#34;Outbound already connected\&amp;#34;)` path instead of failing closed. This causes a remote crash of the networking task (swarm), taking the node&amp;#39;s p2p networking offline until restart. The patch for this vulnerability is formally released as part of v1.3.0. No known workarounds are available.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Nimiq&amp;#39;s network-libp2p is a Nimiq network implementation based on libp2p. Prior to version 1.3.0, `network-libp2p` discovery uses a libp2p `ConnectionHandler` state machine. the handler assumes there is at most one inbound and one outbound discovery substream per connection. if a remote peer opens/negotiate the discovery protocol substream a second time on the same connection, the handler hits a `panic!(\&amp;#34;Inbound already connected\&amp;#34;)` / `panic!(\&amp;#34;Outbound already connected\&amp;#34;)` path instead of failing closed. This causes a remote crash of the networking task (swarm), taking the node&amp;#39;s p2p networking offline until restart. The patch for this vulnerability is formally released as part of v1.3.0. No known workarounds are available.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-34063</guid>
    </item>
  </channel>
</rss>
