Answer in brief
CVE-2026-119793 records a High severity (CVSS 7.5) vulnerability in libp2p: gossipsub creates a permanent topics-map entry per distinct subscription with no cap in the default config. The current sources do not mark it as known exploited. The current feed maps @libp2p/gossipsub (generic), libp2p/js-libp2p (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps @libp2p/gossipsub (generic), libp2p/js-libp2p (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| @libp2p/gossipsubgeneric | <17.0.0 | 17.0.0 |
| libp2p/js-libp2pgeneric | <3.3.9 | 3.3.9 |
Published upstream
Nov 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 17, 2026
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.
Quoted source text, attributed separately from HOL analysis.