NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
LOW severity

CVE-2026-42448 — magic-wormhole

LOW

CVE-2026-42448 is a low-severity (CVSS 3.5) Path Traversal vulnerability in magic-wormhole. A fix is available for magic-wormhole — see the affected versions and patch details below.

wormhole receive, with --output pointing at an existing directory can be path-traversed

Also known asGHSA-cf92-gfcw-6v53PYSEC-2026-2616
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-42448.

EPSS Exploitation Probability

via FIRST.org ↗
0.2%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs9th percentile — riskier than 9% of all scored CVEsHighest risk
0.00%0.26%0.53%0.79%0.0%0.2%Jun 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
🐍magic-wormhole

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Impact

A receiver who specifies "--output <dir>" where that output directory currently exists (as a directory).

Patches

0.24.0 will contain the patch

Workarounds

Ensure local target directories specified by "--output" do not already exist

Resources

Private email and Signal communications from a user. Magic Wormhole thanks @marduc812

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPImagic-wormhole≥ 0.23.0&&< 0.24.00.24.0pip install --upgrade 'magic-wormhole==0.24.0'

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for magic-wormhole, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update magic-wormhole to 0.24.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-42448 is resolved across your whole dependency graph.

  3. Workarounds

    Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

### Impact A receiver who specifies "--output <dir>" where that output directory currently exists (as a directory). ### Patches 0.24.0 will contain the patch ### Workarounds Ensure local target directories specified by "--output" do not already exist ### Resources Private email and Signal communications from a user. Magic Wormhole thanks @marduc812
O3 Security · Impact-Aware SCA

Is CVE-2026-42448 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2026-42448: magic-wormhole — Fixed in 0.24.0