← Back
CVE-2026-46679
high
CVSS 7.5
Vulnerability in @libp2p/gossipsub (CVE-2026-46679)
Summary
vulnerability in @libp2p/gossipsub (CVE-2026-46679). Risk of unauthorized operations or information disclosure. Exploitable via ``handleReceivedSubscription``. Mitigation: upgrade to `15.0.23` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-46679** has been found in @libp2p/gossipsub.
Attackers can target a specific entry point like ``handleReceivedSubscription`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade @libp2p/gossipsub to **15.0.23** or later.
If unsure, ask your IT team or search "@libp2p/gossipsub CVE-2026-46679" on the vendor's site.
CVE-2026-46679 (@libp2p/gossipsub) — CWE-20 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `handleReceivedSubscription` / `Map` / `Set` / `this.topics`
Patched: `15.0.23` — 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/gossipsub. Attackers reach the vulnerable code path via ``handleReceivedSubscription`` without authentication.
📍 Affected scope
@libp2p/gossipsub — . Attack surface: `handleReceivedSubscription` / `Map` / `Set` / `this.topics`.
🔥 Severity
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **15.0.23**.
🛡️ 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/gossipsub' .` 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/gossipsub' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `@libp2p/gossipsub` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade @libp2p/gossipsub to 15.0.23ステージング環境で 15.0.23 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
@libp2p/gossipsub
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"15.0.23"}]}]