Skip to main content
No exploitation reportedFix availableAwaiting NVD analysis

CVE-2026-119793

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

No exploitation reported by the sources we read.

  • Published2026-11-17
  • Fixed in17.0.0
  • WeaknessCWE-400 · CWE-770

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2026-11-1719:10CVE publishedCNA

Versions per branch

OSV
@libp2p/gossipsub
BranchAffectedFixed in
17.0< 17.0.017.0.0

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA2 products

As GitHub_M, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • libp2p js-libp2p
    Affected
    • = < 3.3.9no fix stated
  • @libp2p gossipsub
    Affected
    • = < 17.0.0no fix stated

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-11-17

Fix

  1. Update @libp2p/gossipsub to 17.0.0

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Metasploit modules
none listed
Metasploit Framework

Sources

  • CNACVSS 3.17.52026-11-17
  • CNAweakness (CWE)CWE-400, CWE-7702026-11-17
  • NVDweakness (CWE)CWE-400, CWE-770read 2026-11-17
  • OSVaffected packages—
  • GitHub AdvisoriesadvisoryHIGH2026-11-17

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Published
2026-11-17
Last Modified
2026-11-17
NVD status
Received
GitHub Advisory
GHSA-x2vm-cf3p-m2w8

Frequently asked questions

What is CVE-2026-119793?

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.

Is CVE-2026-119793 actively exploited?

Active exploitation of CVE-2026-119793 has not been confirmed.

What is the CVSS score for CVE-2026-119793?

CVE-2026-119793 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.

Running @libp2p/gossipsub? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record