dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2026-45783

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 16.2.6, an unauthenticated remote peer can exhaust the disk storage of any @libp2p/kad-dht node running in server mode by sending an unbounded stream of PUT_VALUE messages whose keys bypass all content validation. No credentials, no prior relationship, and no protocol deviation beyond a crafted key are required. The victim node's datastore fills until the host disk is exhausted, making the node unavailable. This issue has been patched in version 16.2.6.

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/kad-dht versions prior to 16.2.6 running in server mode, the PUT_VALUE handler lacks proper input validation and storage limits. An unauthenticated remote peer can send arbitrarily crafted keys that bypass content validation, causing unlimited datastore writes until the host disk is exhausted and the node becomes unavailable.

MitigationUpgrade libp2p to version 16.2.6 or later. As a defense-in-depth measure, consider disabling server mode or implementing rate limiting on DHT PUT_VALUE messages until the upgrade is applied.

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. Identify installed libp2p version
    Check the version of the libp2p library or binary in your environment. Common methods: check package.json, go.mod, Cargo.toml, or run 'libp2p version' if CLI available. Compare the version number to 16.2.6.
    Affected if The installed libp2p version is lower than 16.2.6
  2. Verify Kademlia DHT is enabled
    Inspect your libp2p configuration files or code for DHT enablement. Look for DHT module configuration, kad-dht, or Kademlia in the routing/peerDiscovery settings.
    Affected if Kademlia DHT routing is enabled in the configuration
  3. Confirm server mode is active
    Check if the node is configured to accept inbound connections and operate as a DHT server. This is typically controlled by the 'server' or 'bootstrap' option in libp2p config, or the enableServer setting in DHT options.
    Affected if Server mode or bootstrap mode is enabled, allowing the node to respond to DHT queries from other peers
  4. Inspect datastore configuration and usage
    Check the datastore path and current storage usage. Look at disk space consumed by the libp2p datastore directory. On Linux, use 'df -h' on the datastore mount point or 'du -sh <datastore-path>'.
    Affected if Datastore is growing abnormally large or consuming significant disk space from unknown PUT_VALUE operations

You are affected if you are running libp2p versions below 16.2.6 with Kademlia DHT and server mode enabled, and you observe unexpected datastore growth.

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 to version 16.2.6 or later. As a defense-in-depth measure, consider disabling server mode or implementing rate limiting on DHT PUT_VALUE messages until the upgrade is applied.

Recommended fix High confidence

16.2.6

  1. Identify all project dependencies on @libp2p/kad-dht and libp2p packages
  2. Update package.json to specify version 16.2.6 for @libp2p/kad-dht and related libp2p packages
  3. Run npm install or yarn install to update dependencies
  4. Verify the installed version matches 16.2.6 or later
  5. Restart any running libp2p nodes to load the patched version
  6. Monitor disk usage to confirm the vulnerability is mitigated

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45783 — 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-45783 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