libp2p-gossipsub
Affected
- introduced
0.0.0-0, fixed0.49.4(semver)
Fixed versions
0.49.4
Fix
- Fixed version
0.49.4cargo update -p libp2p-gossipsub --precise 0.49.4
Advisory
Also known as: CVE-2026-34219, GHSA-xqmp-fxgv-xvq5
Remote panic in the heartbeat from a large PRUNE backoff
The 0.49.3 fix stopped an overflow when a PRUNE backoff is first stored, but a backoff just small enough to be stored could still overflow later. On each heartbeat, expired backoffs were found with backoff_time + slack > now, which panics when the stored time is close to the largest Instant. A peer that sends one PRUNE with such a backoff crashes the node a heartbeat or so later, and can repeat it after every restart.
The fix caps a remote PRUNE backoff at one hour, uses checked_add for the heartbeat comparison, and replaces other unchecked time arithmetic in the behaviour, peer scoring and time cache with checked or saturating operations. It is in 0.49.4.
Not rated by the source.
0.0.0-0, fixed 0.49.4 (semver)0.49.4
0.49.4cargo update -p libp2p-gossipsub --precise 0.49.4Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: RustSec Advisory Database · CC0-1.0