CVE-2026-35457
Unauthenticated peers can cause unbounded memory growth in libp2p-rust rendezvous before 0.17.1.
Is CVE-2026-35457 being exploited?
Not confirmed. CVE-2026-35457 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.29% probability of exploitation in the next 30 days.
How severe is CVE-2026-35457?
CVE-2026-35457 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-35457?
Yes. A fix has been recorded for CVE-2026-35457. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-35457 affect?
CVE-2026-35457 affects libp2p-rust before 0.17.1, Rendezvous server component. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-35457?
Patch to 0.17.1+ immediately
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Memory exhaustion/DoS via repeated DISCOVER requests; could crash or degrade the rendezvous service.
Patch when possible
- affected< 0.17.1
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.