CVE-2026-119793
Received Received - Intake

Memory Exhaustion in libp2p Gossipsub

Vulnerability report for CVE-2026-119793, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-17

Last updated on: 2026-11-17

Assigner: GitHub, Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-17
Last Modified
2026-11-17
Generated
2026-11-17
AI Q&A
2026-11-17
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
libp2p gossipsub 17.0.0
libp2p js_libp2p *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-770 The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.
CWE-400 The product does not properly control the allocation and maintenance of a limited resource.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in libp2p's Gossipsub protocol allows a remote peer to submit unlimited unsigned subscription requests for distinct topics. The system creates persistent entries for each topic without enforcing limits, causing unbounded memory growth in the topics map. This can lead to out-of-memory conditions and high CPU usage during cleanup when the malicious peer disconnects.

Detection Guidance

Monitor memory usage of the gossipsub process using tools like top, htop, or ps. Check for abnormal growth in the topics map by inspecting the libp2p node's internal state or logs. Look for high CPU usage during peer disconnections, which may indicate cleanup of accumulated topic entries.

Impact Analysis

An attacker could exploit this to consume excessive memory and CPU resources on your system, potentially causing crashes or degraded performance. If your application handles many peers, a single malicious peer could disrupt service for others by exhausting system resources.

Mitigation Strategies

Upgrade to libp2p version 17.0.0 or later to enable the default memory cap for topic subscriptions. If upgrading is not immediately possible, implement custom per-peer limits using the maxTopicBytesPerPeer option to restrict subscription memory usage.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-119793. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...