<?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, 21 Nov 2026 17:57:44 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-407391</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-407391</link>
      <description>EUVD-2026-407391</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-407391</guid>
    </item>
    <item>
      <title>fkie_cve-2026-119793</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-119793</link>
      <description>&lt;p&gt;libp2p is a JavaScript implementation of the libp2p networking stack. Prior to 17.0.0, the @libp2p/gossipsub default configuration allows a connected remote peer to submit unsigned subscription RPC metadata for arbitrarily many distinct topic strings. handleReceivedSubscription in packages/gossipsub/src/gossipsub.ts creates a persistent topics-map entry for each accepted topic, while allowedTopics is unset by default, decodeRpc maxSubscriptions limits only one RPC rather than aggregate topic bytes, and peer scoring has no subscription-volume penalty. A single peer can therefore grow the topics map and committed heap toward out-of-memory conditions, and disconnecting additionally causes removePeer to scan all accumulated topic entries. This issue is fixed in version 17.0.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;libp2p is a JavaScript implementation of the libp2p networking stack. Prior to 17.0.0, the @libp2p/gossipsub default configuration allows a connected remote peer to submit unsigned subscription RPC metadata for arbitrarily many distinct topic strings. handleReceivedSubscription in packages/gossipsub/src/gossipsub.ts creates a persistent topics-map entry for each accepted topic, while allowedTopics is unset by default, decodeRpc maxSubscriptions limits only one RPC rather than aggregate topic bytes, and peer scoring has no subscription-volume penalty. A single peer can therefore grow the topics map and committed heap toward out-of-memory conditions, and disconnecting additionally causes removePeer to scan all accumulated topic entries. This issue is fixed in version 17.0.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-119793</guid>
    </item>
    <item>
      <title>GHSA-x2vm-cf3p-m2w8 — libp2p: gossipsub creates a permanent topics-map entry per distinct subscription with no cap in the default config</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-x2vm-cf3p-m2w8</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @libp2p/gossipsub&lt;/p&gt;
&lt;p&gt;### Summary
A single gossipsub peer can grow a node&amp;#39;s `topics` map without bound by flooding subscription RPCs, because the default configuration has no global, per-peer, or topic-length cap and peer scoring does not penalise subscription volume. The peer is never greylisted, so the growth continues toward OOM.&lt;/p&gt;
&lt;p&gt;### Details
`handleReceivedSubscription` (`packages/gossipsub/src/gossipsub.ts:1028`, line 1036) runs `this.topics.set(topic, new Set())` for every distinct topic string:&lt;/p&gt;
&lt;p&gt;```ts
private handleReceivedSubscription (from, topic, subscribe) {
  let topicSet = this.topics.get(topic)
  if (subscribe) {
    if (topicSet == null) {
      topicSet = new Set()
      this.topics.set(topic, topicSet)   // no global cap, no per-peer cap
    }
    topicSet.add(from.toString())
  }
}
```&lt;/p&gt;
&lt;p&gt;The only topical gate (`gossipsub.ts:981`, `if (this.allowedTopics != null &amp;amp;&amp;amp; !this.allowedTopics.has(topic)) return`) is skipped when `allowedTopics` is null — the default. Subscriptions are unsigned RPC metadata (no signature needed); `decodeRpc`&amp;#39;s per-RPC limit caps count (`maxSubscriptions = 5000`) but not topic-string length or aggregate size; and the peer-scoring components P1–P7 have no subscription-volume term, so the attacker&amp;#39;s score stays at 0 (above the `graylistThreshold` of −80) and `acceptFrom` keeps returning true. Verified on js-libp2p commit `a04f5e0`, where `@libp2p/gossipsub` reads `16.0.4`.&lt;/p&gt;
&lt;p&gt;### PoC
Full PoC attached (`gossipsub-topics-unbounded-growth-poc.tar.gz`). Build the…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @libp2p/gossipsub&lt;/p&gt;
&lt;p&gt;### Summary
A single gossipsub peer can grow a node&amp;#39;s `topics` map without bound by flooding subscription RPCs, because the default configuration has no global, per-peer, or topic-length cap and peer scoring does not penalise subscription volume. The peer is never greylisted, so the growth continues toward OOM.&lt;/p&gt;
&lt;p&gt;### Details
`handleReceivedSubscription` (`packages/gossipsub/src/gossipsub.ts:1028`, line 1036) runs `this.topics.set(topic, new Set())` for every distinct topic string:&lt;/p&gt;
&lt;p&gt;```ts
private handleReceivedSubscription (from, topic, subscribe) {
  let topicSet = this.topics.get(topic)
  if (subscribe) {
    if (topicSet == null) {
      topicSet = new Set()
      this.topics.set(topic, topicSet)   // no global cap, no per-peer cap
    }
    topicSet.add(from.toString())
  }
}
```&lt;/p&gt;
&lt;p&gt;The only topical gate (`gossipsub.ts:981`, `if (this.allowedTopics != null &amp;amp;&amp;amp; !this.allowedTopics.has(topic)) return`) is skipped when `allowedTopics` is null — the default. Subscriptions are unsigned RPC metadata (no signature needed); `decodeRpc`&amp;#39;s per-RPC limit caps count (`maxSubscriptions = 5000`) but not topic-string length or aggregate size; and the peer-scoring components P1–P7 have no subscription-volume term, so the attacker&amp;#39;s score stays at 0 (above the `graylistThreshold` of −80) and `acceptFrom` keeps returning true. Verified on js-libp2p commit `a04f5e0`, where `@libp2p/gossipsub` reads `16.0.4`.&lt;/p&gt;
&lt;p&gt;### PoC
Full PoC attached (`gossipsub-topics-unbounded-growth-poc.tar.gz`). Build the…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-x2vm-cf3p-m2w8</guid>
    </item>
  </channel>
</rss>
