CVE
js-libp2p memory exhaustion via unbounded topics in gossipsub
Affects js-libp2p and @libp2p/gossipsub in the default configuration, where allowedTopics is unset and no cap is set. Fixed in js-libp2p 3.3.9 and @libp2p/gossipsub 17.0.0.
Written by a model from the sources below. Verify against them.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Exploited
- No known exploitation
- Fix
- Fixed in js-libp2p 3.3.9 · gossipsub 17.0.0
- Who is exposed
- Default setups
Do first: Check every install: default setups are affected.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 30/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Default setups
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the gossipsub package of libp2p's js-libp2p, a remote peer that has connected to the node can, without logging in, send subscriptions for arbitrarily many distinct topic names under the default configuration, and each one leaves a permanent entry in memory. This can drive memory use toward out-of-memory conditions, and disconnecting the peer forces a scan of all the accumulated entries.
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.
Who should check
Teams running @libp2p/gossipsub or js-libp2p below 17.0.0 with the default gossipsub configuration, including any node accepting connections from untrusted peers
“Every node running default gossipsub is affected”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure22/25Default setups, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.5/10CVSS 7.5
- No patch0/5No signal
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
What to do
Check every install: default setups are affected.
Upgrade to a fixed version: js-libp2p 3.3.9 · gossipsub 17.0.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-119793 (libp2p: gossipsub creates a permanent topics-map entry per distinct subscription with no cap in the default config), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-119793 (entry last updated 2026-11-17):
Affected:
- libp2p js-libp2p: fixed in 3.3.9
- @libp2p gossipsub: fixed in 17.0.0
Fixed versions: 3.3.9, 17.0.0.
Conditions (all must be true for the bug to be hit):
- Default gossipsub configuration, where no global, per-peer, or topic-length cap is set (source: https://github.com/libp2p/js-libp2p/security/advisories/GHSA-x2vm-cf3p-m2w8)
- allowedTopics left unset (null), which is the default (source: https://github.com/libp2p/js-libp2p/security/advisories/GHSA-x2vm-cf3p-m2w8)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-119793 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-119793 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/libp2p/js-libp2p/security/advisories/GHSA-x2vm-cf3p-m2w8
- https://github.com/libp2p/js-libp2p/pull/3593
- https://github.com/libp2p/js-libp2p/commit/d5534174d8b7d23ac1bd45a7e738664fbfb0cf4c
- https://github.com/libp2p/js-libp2p/releases/tag/gossipsub-v17.0.0
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-119793
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-119793"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- libp2p js-libp2p
fixed in 3.3.9
- @libp2p gossipsub
fixed in 17.0.0
Evidence 6
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 3
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-119793
Is CVE-2026-119793 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
Gossipsub keeps a permanent entry in its topics map for each distinct subscription, and with no cap a single connected remote peer can make that map and the heap grow without bound, pushing the node toward out-of-memory conditions. Disconnecting a peer also adds CPU cost because of a full sweep.Source: github.com
Which versions are affected by CVE-2026-119793?
js-libp2p: before 3.3.9. gossipsub: before 17.0.0.Source: cve.now feed data
Am I affected, and how do I check?
The issue applies to the default gossipsub configuration, where no global, per-peer, or topic-length cap is set and allowedTopics is left unset (null). To check, look at the installed js-libp2p and @libp2p/gossipsub versions and whether allowedTopics is set in the gossipsub options.Source: github.com
How do I fix CVE-2026-119793?
Upgrade js-libp2p to 3.3.9 or later, or @libp2p/gossipsub to 17.0.0 or later.Source: github.com