Arbitrary file overwrite via unnormalized received filename
Published Mar 12, 2026 · Updated Mar 12, 2026
Path traversal in Magic Wormhole 0.21.0 through 0.22.0 allows remote authenticated users to overwrite local files during receipt. The receive path uses the sender-supplied filename to choose the destination after a refactor removed receiver-side basename() normalization. A receiver must run wormhole receive, enter the shared code, and accept the transfer; relay servers cannot exploit the flaw.
Summary
What happened
Path traversal in Magic Wormhole 0.21.0 through 0.22.0 allows remote authenticated users to overwrite local files during receipt. The receive path uses the sender-supplied filename to choose the destination after a refactor removed receiver-side basename() normalization. A receiver must run wormhole receive, enter the shared code, and accept the transfer; relay servers cannot exploit the flaw.
The record
- CVE
- CVE-2026-32116
- Published
- Mar 12, 2026
- Updated
- Mar 12, 2026
- Vendor
- Magic Wormhole
- Product
- Magic Wormhole
- Classifications
- CWE-22, T1203
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 12, 2026CVE publishedPublication date reported by the CVE source.
- Mar 12, 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.21.0, < 0.23.0
What conditions does exploitation require?
What is affected?
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