CVE-2026-33040 affects libp2p-rust, the official Rust implementation of the libp2p networking stack, in versions prior to 0.49.3. The flaw is in the Gossipsub implementation's handling of PRUNE control messages: it accepts attacker-controlled backoff values and performs unchecked time arithmetic when updating and storing backoff state. By sending a specially crafted PRUNE message containing an extremely large backoff value, such as u64::MAX, a remote attacker can trigger Duration/Instant overflow in the backoff update logic. This overflow causes a panic in the networking state machine, terminating or crashing the affected application path. The issue is remotely reachable over a normal libp2p connection and does not require authentication.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.