Path Traversal in magic-wormhole (CVE-2026-32116)
Summary
Path traversal in magic-wormhole (CVE-2026-32116). Risk of unauthorized operations or information disclosure. Exploitable via filename. Mitigation: upgrade to 0.23.0 or later.
Original description
The description as published by the source.
Magic Wormhole makes it possible to get arbitrary-sized files and directories from one computer to another. From 0.21.0 to before 0.23.0, receiving a file (wormhole receive) from a malicious party could result in overwriting critical local files, including ~/.ssh/authorized_keys and .bashrc. This could be used to compromise the receiver's computer. Only the sender of the file (the party who runs wormhole send) can mount the attack. Other parties (including the transit/relay servers) are excluded by the wormhole protocol. This vulnerability is fixed in 0.23.0.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-32116 has been found in magic-wormhole.
Attackers can target a specific entry point like filename over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade magic-wormhole to 0.23.0 or later.
If unsure, ask your IT team or search "magic-wormhole CVE-2026-32116" on the vendor's site.
CVE-2026-32116 (magic-wormhole) — CWE-22
Attack surface: filename
Patched: 0.23.0 — 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.
Path traversal (CWE-22) exists in magic-wormhole. Attackers reach the vulnerable code path via filename.
Check the vendor advisory for the affected versions of magic-wormhole. Attack surface: filename.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.23.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'magic-wormhole' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'magic-wormhole' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
magic-wormholeを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade magic-wormhole to 0.23.0ステージング環境で 0.23.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Ubuntu UBUNTU-CVE-2026-32116 magic-wormhole
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com