CVE-2026-89146
libp2p-rendezvous through 0.17.1 fails to validate registration TTL values in discovery responses, allowing attackers to trigger timer arithmetic overflow.
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (0.43%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
Description
libp2p-rendezvous through 0.17.1 fails to validate registration TTL values in discovery responses, allowing attackers to trigger timer arithmetic overflow. A malicious rendezvous server can send a discovery response with an unbounded TTL value that causes the client node process to panic when computing the expiry timer.
- CVSS 4.0
- 8.7 HIGHCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/M
- EPSS
- 0.43% probability · 36th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-190, CWE-617
- Source
- disclosure@vulncheck.com
References
- https://docs.rs/crate/libp2p-rendezvous/0.17.1/source/src/client.rs
- https://gist.github.com/thesmartshadow/25ef03f7ebbd12118a9d27695c885989
- https://github.com/libp2p/rust-libp2p
- https://www.vulncheck.com/advisories/libp2p-rendezvous-through-0.17.1-denial-of-service-via-unbounded-registration-ttl-in-discovery-responses
- https://gist.github.com/thesmartshadow/25ef03f7ebbd12118a9d27695c885989
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.