← Back
CVE-2026-45783
high
CVSS 7.5
Vulnerability in @libp2p/kad-dht (CVE-2026-45783)
Summary
vulnerability in @libp2p/kad-dht (CVE-2026-45783). Risk of unauthorized operations or information disclosure. Exploitable via ``PUT_VALUE``. Mitigation: upgrade to `16.2.6` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-45783** has been found in @libp2p/kad-dht.
Attackers can target a specific entry point like ``PUT_VALUE`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade @libp2p/kad-dht to **16.2.6** or later.
If unsure, ask your IT team or search "@libp2p/kad-dht CVE-2026-45783" on the vendor's site.
CVE-2026-45783 (@libp2p/kad-dht) — CWE-20 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `PUT_VALUE` / `verifyRecord` / `BYPASS` / `RATE`
Patched: `16.2.6` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-20) exists in @libp2p/kad-dht. Attackers reach the vulnerable code path via ``PUT_VALUE`` without authentication.
📍 Affected scope
@libp2p/kad-dht — . Attack surface: `PUT_VALUE` / `verifyRecord` / `BYPASS` / `RATE`.
🔥 Severity
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **16.2.6**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r '@libp2p/kad-dht' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@libp2p/kad-dht' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `@libp2p/kad-dht` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade @libp2p/kad-dht to 16.2.6ステージング環境で 16.2.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
@libp2p/kad-dht
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"16.2.6"}]}]