CVE-2026-119793

7.5High

Published 17 Nov 2026 · NVD status: Received · AI triage by gemini-3.1-flash-lite

7.5CVSS

High

0CVSS v3.110

Attack vector
Network
Complexity
Low
Privileges
None
User action
None
Impact
High impact on availability
Weakness
CWE-400, CWE-770

What an attacker gets

Remote attackers can crash your service by exhausting memory through a flood of subscription topics. No authentication is required to trigger this denial-of-service condition.

Root cause

The gossipsub implementation lacks limits on the number of subscription topics a peer can register, allowing the heap to grow indefinitely.

Affected versions

@libp2p/gossipsub prior to 17.0.0

CVSS v3.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Fix & remediation

Upgrade @libp2p/gossipsub to version 17.0.0 or later. If you cannot upgrade immediately, configure the allowedTopics option to restrict the number of accepted subscription topics.

remediation — bash
$ npm install @libp2p/gossipsub@latest

AI-suggested. Run it in staging first and check it against the vendor advisory. Why?

NVD 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.

References

Source: nvd.nist.gov/vuln/detail/CVE-2026-119793