CVE-2026-34219
MediumCVSS 5.9Exploitation Probability (EPSS)
Low risk32th percentile - higher than 32% of all known CVEs
Summary
In libp2p-rust before version 0.49.4, the Gossipsub implementation contains a remotely reachable panic in backoff expiry handling. After receiving a crafted PRUNE message with a near-maximum backoff value, the implementation performs unchecked time arithmetic, leading to overflow and panic.
Risk Assessment
An attacker can crash a Gossipsub node, causing denial of service (DoS) and potentially disrupting the libp2p network.
Recommendation
Update libp2p-rust to version 0.49.4 or later.
Other vulnerabilities in libp2p-rust
See all- CVE-2026-33040High
In versions prior to 0.49.3, the Gossipsub implementation in libp2p-rust accepts attacker-controlled PRUNE backoff values, which may lead to time overflow and panic in the networking state machine.
- CVE-2026-95859High
In libp2p-rust, Gossipsub GRAFT control-message handling unconditionally adds attacker-supplied topic hashes to connected_peer.topics without confirming prior subscription. A remote unauthenticated peer can repeatedly send novel GRAFT topics, causing cumulative per-peer memory growth that can exhaust process memory and cause denial of service.
- CVE-2026-61544High
In libp2p-rust, libp2p-quic could panic during an inbound QUIC handshake when a remote peer presented a valid short-lived libp2p TLS certificate and delayed the final TLS 1.3 handshake fragment until after the certificate expired. In the Quinn post-handshake upgrade path, the code called libp2p_tls::certificate::parse a second time and used expect on the result; the repeated wall-clock validity check could reject the now-expired certificate, causing the expect call to terminate any application exposing an affected libp2p-quic listener. Fixed in 0.13.1.
Original NVD description (English source)
libp2p-rust is the official rust language Implementation of the libp2p networking stack. Prior to version 0.49.4, the Rust libp2p Gossipsub implementation contains a remotely reachable panic in backoff expiry handling. After a peer sends a crafted PRUNE control message with an attacker-controlled, near-maximum backoff value, the value is accepted and stored as an Instant near the representable upper bound. On a later heartbeat, the implementation performs unchecked Instant + Duration arithmetic (backoff_time + slack), which can overflow and panic with: overflow when adding duration to instant. This issue is reachable from any Gossipsub peer over normal TCP + Noise + mplex/yamux connectivity and requires no further authentication beyond becoming a protocol peer. This issue has been patched in version 0.49.4.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS