Path Traversal in magic-wormhole (CVE-2026-42448)
Summary
Path traversal in magic-wormhole (CVE-2026-42448). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.24.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. Prior to 0.24.0, there is a path traversal when a receiver who specifies "--output " where that output directory currently exists (as a directory). This vulnerability is fixed in 0.24.0.
Source: NIST National Vulnerability Database NVD GitHub Advisory
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-42448 has been found in magic-wormhole.
Risk of unauthorized operations or information disclosure. CVSS score: 3.5/10.
What to do: upgrade magic-wormhole to 0.24.0 or later.
If unsure, ask your IT team or search "magic-wormhole CVE-2026-42448" on the vendor's site.
CVE-2026-42448 (magic-wormhole) — CWE-22 / CVSS v3 3.5
Attack vector: remote (network-reachable)
Patched: 0.24.0 — apply immediately
Workaround: Ensure local target directories specified by "--output" do not already exist
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.
Check the vendor advisory for the affected versions of magic-wormhole.
Severity: Low (CVSS 3.5/10). Risk of unauthorized operations or information disclosure.
Update to 0.24.0.
Workaround: Ensure local target directories specified by "--output" do not already exist
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 temporary workaround mitigate
Ensure local target directories specified by "--output" do not already existパッチが適用されるまでの応急処置として、Ensure local target directories specified by "--output" do not already exist を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade magic-wormhole to 0.24.0ステージング環境で 0.24.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com