File overwrite via omitted receiver basename
Published May 26, 2026 · Updated May 26, 2026
Path traversal in Magic Wormhole 0.23.0 allows remote authenticated users to write received files outside an existing output directory. When --output names an existing directory, the receive path joins it with the sender-controlled filename without first reducing that name to its basename. Exploitation requires the receiver to enter the sender's wormhole code, select an existing directory, and accept the transfer; the resulting write alters local file integrity.
Summary
What happened
Path traversal in Magic Wormhole 0.23.0 allows remote authenticated users to write received files outside an existing output directory. When --output names an existing directory, the receive path joins it with the sender-controlled filename without first reducing that name to its basename. Exploitation requires the receiver to enter the sender's wormhole code, select an existing directory, and accept the transfer; the resulting write alters local file integrity.
The record
- CVE
- CVE-2026-42448
- Published
- May 26, 2026
- Updated
- May 26, 2026
- Vendor
- Magic Wormhole
- Product
- Magic Wormhole
- Classifications
- CWE-22
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 26, 2026CVE publishedPublication date reported by the CVE source.
- May 26, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.24.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo