# libp2p-gossipsub: Remote crash via unchecked Instant overflow in heartbeat backoff expiry handling

Advisory record · `GHSA-xqmp-fxgv-xvq5`

- **Identifiers:** `GHSA-xqmp-fxgv-xvq5` · `CVE-2026-34219` · `RUSTSEC-2026-0537`
- **State:** Confirmed
- **Severity:** CVSS 8.2 High
- **Critical:** No
- **Weakness (CWE):** [CWE-190](https://cwe.mitre.org/data/definitions/190.html) · [CWE-617](https://cwe.mitre.org/data/definitions/617.html)
- **Tags:** [Memory corruption](https://agentprime.io/advisories/tag/memory-corruption.md) · [Denial of service](https://agentprime.io/advisories/tag/dos.md)
- **Published:** 30 Mar 2026
- **Updated:** 13 Nov 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 30 Mar 2026, 13:04 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `libp2p-gossipsub` (crates.io): affected `<0.49.4`; fixed in `0.49.4`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Versions of libp2p-gossipsub before 0.49.4 are vulnerable. A remote peer that has established a Gossipsub session with a node can send a crafted PRUNE control message with an oversized backoff value, which causes a panic during the next heartbeat and crashes the node. Upgrade libp2p-gossipsub to version 0.49.4 or later.

Written 8 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 8.2 High, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0058, the 48th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:18 UTC: First seen by agentprime
- 31 Oct 2026, 15:18 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-xqmp-fxgv-xvq5)

## Sources

- [GitHub Advisory Database: GHSA-xqmp-fxgv-xvq5](https://github.com/advisories/GHSA-xqmp-fxgv-xvq5)
- [OSV: GHSA-xqmp-fxgv-xvq5](https://osv.dev/vulnerability/GHSA-xqmp-fxgv-xvq5)
- <https://github.com/libp2p/rust-libp2p/security/advisories/GHSA-xqmp-fxgv-xvq5>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-34219>
- <https://github.com/advisories/GHSA-gc42-3jg7-rxr2>
- <https://github.com/libp2p/rust-libp2p>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-xqmp-fxgv-xvq5>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-xqmp-fxgv-xvq5/>. Everything for agents: <https://agentprime.io/llms.txt>.
