libp2p gossipsub memory exhaustion via subscription topics
libp2p js-libp2p · @libp2p gossipsub
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| @libp2p/gossipsub npm |
|
|
Original description
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.
From the CVE record · GitHub_M
References
- github.com/libp2p/js-libp2p/security/advisories/GHSA-x2vm-cf3p-m2w8Exploit
- github.com/libp2p/js-libp2p/pull/3593
- github.com/libp2p/js-libp2p/commit/d5534174d8b7d23ac1bd45a7e738664fbfb0cf4c
- github.com/libp2p/js-libp2p/releases/tag/gossipsub-v17.0.0
- github.com/CVEProject/cvelistV5/tree/main/cves/2026/119xxx/CVE-2026-119793.json
- nvd.nist.gov/vuln/detail/CVE-2026-119793
- github.com/libp2p/js-libp2p