Skip to main content
VulnerabilityPublished Updated

CVE-2026-35405: rust-libp2p · Unthrottled Resource Allocation

Affects rust-libp2pSource CVE Database V5

0
Compare

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

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.17.1
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 7 Apr 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 30 Oct 2026.

What to do

Upgrade rust-libp2p and libp2p/rust-libp2p to 0.17.1.

Affected software

ProductAffectedFixed in
libp2prust-libp2pAffected
  • <0.17.1
Fixed in
  • 0.17.1
crates.iolibp2p/rust-libp2ppkg:cargo/libp2p/rust-libp2pOther threatsAffected
  • <0.17.1
Fixed in
  • 0.17.1

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

AI-suggested

Upgrade libp2p-rust to version 0.17.1 or later, where the vulnerability is fixed by implementing limits on namespace registrations per peer. No other mitigation is indicated or required as the fix is available.

Description

libp2p-rust is the official rust language Implementation of the libp2p networking stack. Prior to 0.17.1, libp2p-rendezvous server has no limit on how many namespaces a single peer can register. A malicious peer can just keep registering unique namespaces in a loop and the server happily accepts every single one allocating memory for each registration with no pushback. Keep doing this long enough (or with multiple sybil peers) and the server process gets OOM killed. This vulnerability is fixed in 0.17.1.

References

Community reviews

Loading reviews…