CVE-2026-35405: libp2p-rust is the official rust language Implementation of the libp2p networking stack

Q: How do I fix CVE-2026-35405?

libp2p: upgrade to 0.17.1. Exact commands for each OS are on this page.

Q: Is CVE-2026-35405 being exploited?

CVE-2026-35405 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-35405 affect?

CVE-2026-35405 affects libp2p. Severity is high (CVSS 7.5). 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 u

Q: How urgent is CVE-2026-35405?

Priority 45/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

This week

HIGH 7.5REMOTEUPGRADE

CVE-2026-35405 is a high-severity flaw (CVSS 7.5) affecting libp2p. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 pro

Why this priority

High severity
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.4% (top 66%)
CISA exploited list	No
Weakness	CWE-770
Published	2026-04-07
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: protocol

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-04-07 15:17 UTCPublished CVE record published
2026-06-17 10:40 UTCUpdated Record last modified

protocol libp2p UPGRADE

Affected: < 0.17.1

Fixed in: 0.17.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy libp2p || rpm -q libp2p || libp2p --version

2. UPGRADE to 0.17.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade libp2p

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade libp2p

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-35405?

libp2p: upgrade to 0.17.1. Exact commands for each OS are on this page.

Is CVE-2026-35405 being exploited?

CVE-2026-35405 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-35405 affect?

CVE-2026-35405 affects libp2p. Severity is high (CVSS 7.5). 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 u

How urgent is CVE-2026-35405?

Priority 45/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

Related CVEs

CVE-2026-35457 HIGH 8.2 UPGRADE libp2p-rust is the official rust language Implementation of the libp2p networking stack

References

← Back to latest CVEs