Skip to main content
VulnerabilityPublished Updated

CVE-2026-35457: Libp2p rendezvous · Rendezvous server stored an unlimited number of DISCOVER cookies

Affects libp2p-rendezvousSource GCVE Database

0
Compare
Authoritative record:CVE-2026-35457· High 8.2

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

Data as of 13 Nov 2026, 13:16 UTC

CVSS 3.1 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 0.17.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 13 Nov 2026.

What to do

Upgrade libp2p-rendezvous to 0.17.1.

Affected software

ProductAffectedFixed in
crates.iolibp2p-rendezvouspkg:cargo/libp2p-rendezvousOther threatsAffected
  • >=0.0.0-0 <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-rendezvous to version 0.17.1 or later, which includes a fix that limits the number of stored DISCOVER cookies using a fixed-size LRU cache. No other mitigation is required as the vulnerability is addressed by this official fix.

Description

A vulnerability in libp2p-rendezvous prior to version 0.17.1 allows unauthenticated peers to cause unbounded memory growth on the rendezvous server by sending repeated DISCOVER requests. This occurs because the server stored an unlimited number of pagination cookies without eviction. The issue is fixed in version 0.17.1 by implementing a fixed-size LRU cache for cookies.

References

Community reviews

Loading reviews…