Skip to main content
CVE-2026-119793VulnerabilityPublished

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

Affects @libp2p/gossipsubSource GCVE Database

0
Compare
Authoritative record:CVE-2026-119793· High 7.5

Not known to be exploited · CVSS 7.5 High : upgrade to 17.0.0 soon.

Data as of 17 Nov 2026, 21:50 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.17.5
Patch
Available – fixed in 17.0.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Upgrade @libp2p/gossipsub to 17.0.0.

Affected software

ProductAffectedFixed in
npm@libp2p/gossipsubAffected
  • <17.0.0
Fixed in
  • 17.0.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available in @libp2p/gossipsub version 17.0.0 that addresses this issue. Users should upgrade to version 17.0.0 or later. The fix includes bounding the size of the topics map, implementing per-peer subscription caps with penalties in peer scoring to enable greylisting, enforcing topic-string length limits, and optionally using an allowlist for topics to deny-by-default. Additionally, the removePeer function's topic iteration has been optimized to avoid blocking. Until patched, users can mitigate by setting allowedTopics to a non-null allowlist to reject unauthorized topics.

Description

A vulnerability in the default configuration of @libp2p/gossipsub (versions before 17.0.0) allows a single peer to cause unbounded growth of the node's topics map by flooding subscription RPCs. This occurs because there is no cap on the number of topics, no per-peer subscription limit, and no penalty in peer scoring for subscription volume. The resulting resource exhaustion can lead to out-of-memory conditions and increased CPU usage during peer disconnection.

References

Community reviews

Loading reviews…