GHSA-vrx6-jcp8-vm7m json
Unbounded backoff state from PRUNE messages for unknown topics
published 29d ago modified 4d ago also RUSTSEC-2026-0534
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
A PRUNE control message names topics and asks for a backoff on each. The handler recorded a backoff for every named topic, including topics the local node had never joined. A peer can send PRUNEs naming many new short topic IDs with a long backoff. Each pair is kept until the backoff expires, up to an hour, even after the peer disconnects, so a stream of PRUNEs, possibly from many peer IDs, can use up the node's memory. Peer scoring does not penalise these messages.
The fix ignores PRUNE entries for topics that are not in the node's mesh. It is in 0.50.1, and was backported to the main branch in libp2p/rust-libp2p#6707.
Patch / fix
- crates.io libp2p-gossipsub 0.50.1
- github.com/libp2p/rust-libp2p@9c64782 commit
- github.com/libp2p/rust-libp2p#6707 pull request
Is GHSA-vrx6-jcp8-vm7m in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | libp2p-gossipsub | >=0.0.0-0, <0.50.1 |
0.50.1 |
References
Sources
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.