dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2026-46679

HIGH · 7.5 CVSS v3.1 Published 2026-06-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
libp2p is a JavaScript Implementation of libp2p networking stack. Prior to version 15.0.23, three cooperating omissions in @libp2p/gossipsub allow an unauthenticated single peer to exhaust the Node.js heap of any gossipsub node with default options. This issue has been patched in version 15.0.23.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In @libp2p/gossipsub versions prior to 15.0.23, three missing validation checks allow an unauthenticated remote peer to trigger heap exhaustion on any gossipsub node using default configuration, resulting in denial of service.

MitigationUpgrade @libp2p/gossipsub to version 15.0.23 or later to apply the patched code that addresses the three validation omissions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate @libp2p/gossipsub in dependencies
    Inspect your project's package.json file, or run 'npm list @libp2p/gossipsub' or 'yarn list @libp2p/gossipsub' to list the installed package and its version
    Affected if @libp2p/gossipsub appears in dependencies with a version number lower than 15.0.23
  2. Verify gossipsub protocol is enabled
    Examine your libp2p configuration code or config file to confirm that the gossipsub protocol is included in the protocols list or enabled by default in your setup
    Affected if gossipsub is listed as an enabled protocol or is used without explicit disablement
  3. Confirm network exposure to remote peers
    Check your libp2p node configuration for listen addresses and connection settings. Verify if the node accepts incoming connections from untrusted remote peers (not limited to localhost or trusted peers only)
    Affected if The node is configured to accept remote peer connections on public or untrusted networks
  4. Check heap memory limits and behavior
    Monitor node memory usage during normal operation or inspect startup flags for heap limits (--max-old-space-size). Under this vulnerability, heap exhaustion occurs when processing malicious gossipsub messages from remote peers
    Affected if Running with default memory settings and exposed to untrusted network, the node may exhibit rapid heap growth or crash when receiving crafted gossipsub messages

A user is affected if @libp2p/gossipsub version is below 15.0.23 AND gossipsub is enabled AND the node accepts remote peer connections on an untrusted network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade @libp2p/gossipsub to version 15.0.23 or later to apply the patched code that addresses the three validation omissions.

Recommended fix High confidence

@libp2p/gossipsub version 15.0.23

  1. Check current version of @libp2p/gossipsub in your project (e.g., npm list @libp2p/gossipsub)
  2. Upgrade @libp2p/gossipsub to version 15.0.23 or later using your package manager (e.g., npm install @libp2p/[email protected])
  3. Verify the upgrade was successful by checking the installed version
  4. Test that your gossipsub functionality works correctly with the updated dependency
  5. Ensure any dependent libp2p packages are also compatible with the upgrade
Caveat Review libp2p release notes for 15.0.23 to check for any breaking changes in your specific use case

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,340
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,144.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46679 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-46679 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data