Home/Research/Post

GHSA-x2vm-cf3p-m2w8: libp2p: gossipsub creates a permanent topics-map entry per distinct subscription with no cap in the default config

  • Severity: HIGH
  • CVE: CVE-2026-119793
  • Ecosystems: npm
  • Packages: @libp2p/gossipsub

### Summary
A single gossipsub peer can grow a node’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.

### Details
`handleReceivedSubscription` (`packages/gossipsub/src/gossipsub.ts:1028`, line 1036) runs `this.topics.set(topic, new Set())` for every distinct topic string:

“`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())
}
}
“`

The only topical gate (`gossipsub.ts:981`, `if (this.allowedTopics != null && !this.allowedTopics.has(topic)) return`) is skipped when `allowedTopics` is null — the default. Subscriptions are unsigned RPC metadata (no signature needed); `decodeRpc`’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’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`.

### PoC
Full PoC attached (`gossipsub-topics-unbounded-growth-poc.tar.gz`). Build the js-libp2p monorepo at the…

Source: GitHub Security Advisories · 2026-11-17