Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.5amended

@libp2p/kad-dht: Unvalidated PUT_VALUE records allow unbounded disk exhaustion on DHT server nodes

CVE-2026-45783GHSA-32mq-hpph-xfvr

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (@libp2p/kad-dht 16.2.6), 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
7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
  • CVE-2026-45783: 0.35% estimated exploitation activity in the next 30 days; percentile 29.18 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary 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 PUTVALUE 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. Details Two cooperating defects combine to produce the vulnerability. Defect 1: verifyRecord silent early-return (packages/kad-dht/src/record/validators.ts:19-21) Legitimate DHT keys (/pk/<multihash, /ipns/<peerId) have exactly 3 slash-delimited parts and are routed to registered validators. Any key whose UTF-8 representation splits into fewer than 3 parts, single-byte keys, or any value without two / characters, thus, bypasses validation entirely and is written to the datastore unconditionally. There is no audit log and no error returned to the caller. Defect 2: Unbounded RPC…

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

    Amended from ghsa record GHSA-32mq-hpph-xfvr

  2. Revision 1 · created ·

    Published from osv record GHSA-32mq-hpph-xfvr

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-45783

Advisory: @libp2p/kad-dht: Unvalidated PUT_VALUE records allow unbounded disk exhaustion on DHT server nodes
IDs: CVE-2026-45783, GHSA-32mq-hpph-xfvr
Record: https://patchnext.com/advisories/cve-2026-45783 (revision 2, source checked 26 Oct 2026, 12:55 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @libp2p/kad-dht 16.2.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @libp2p/kad-dht: affected < 16.2.6; fixed in 16.2.6

## Suggested inspection (read-only)
- `npm ls @libp2p/kad-dht --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## 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/kad-dht.
- 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/GHSA-32mq-hpph-xfvr (OSV record GHSA-32mq-hpph-xfvr lists affected ranges: npm @libp2p/kad-dht >=0 <16.2.6 (fixed))
- Verified: https://github.com/advisories/GHSA-32mq-hpph-xfvr (GitHub-reviewed advisory GHSA-32mq-hpph-xfvr lists affected ranges: npm @libp2p/kad-dht >=0 <16.2.6)

Commands are suggestions: review each one before running it.

Loading voting…