Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

Unbounded memory growth from GRAFT messages for unsubscribed topics

CVE-2026-95859GHSA-g3g5-x568-qvqx

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (libp2p-gossipsub 0.49.5), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

When a GRAFT control message arrived, every topic it named was added to that peer's set of topics, on the assumption that a peer grafting us must be subscribed. Nothing checked that the peer had subscribed, and subscription filters only apply to SUBSCRIBE messages. A peer can keep sending GRAFTs with new short topic IDs over one connection, and the set grows until the peer unsubscribes or disconnects. Memory grows without bound and the node can be killed for running out of memory. The fix no longer records topics from GRAFT messages and drops a GRAFT for a topic the peer has not subscribed to. It also makes `MaxCountSubscriptionFilter` the default subscription filter. It is in 0.49.5, and was backported to the 0.50 line before 0.50.0.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from osv record RUSTSEC-2026-0536

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-95859

Advisory: Unbounded memory growth from GRAFT messages for unsubscribed topics
IDs: CVE-2026-95859, GHSA-g3g5-x568-qvqx
Record: https://patchnext.com/advisories/cve-2026-95859 (revision 1, source checked 14 Nov 2026, 08:25 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: libp2p-gossipsub 0.49.5. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io libp2p-gossipsub: affected >= 0.0.0-0, < 0.49.5; fixed in 0.49.5

## Suggested inspection (read-only)
- crates.io libp2p-gossipsub: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on libp2p-gossipsub.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/RUSTSEC-2026-0536 (OSV record RUSTSEC-2026-0536 lists affected ranges: crates.io libp2p-gossipsub >=0.0.0-0 <0.49.5 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…