Arbitrary file overwrite via unsanitized archive paths
Published Jul 15, 2025 · Updated Apr 1, 2026
Path traversal in Vim before 9.1.1551 allows attackers to overwrite arbitrary files by editing a crafted zip archive. The zip#Write function accepts leading ../ components from an archive member name and writes the buffer with :w! outside its temporary directory. Exploitation requires a user to open the archive, select the malicious member, and save it; resulting writes inherit the Vim process's permissions.
Summary
What happened
Path traversal in Vim before 9.1.1551 allows attackers to overwrite arbitrary files by editing a crafted zip archive. The zip#Write function accepts leading ../ components from an archive member name and writes the buffer with :w! outside its temporary directory. Exploitation requires a user to open the archive, select the malicious member, and save it; resulting writes inherit the Vim process's permissions.
The record
- CVE
- CVE-2025-53906
- Published
- Jul 15, 2025
- Updated
- Apr 1, 2026
- Vendor
- Vim
- Product
- Vim
- Classifications
- CWE-22, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 15, 2025CVE publishedPublication date reported by the CVE source.
- Apr 1, 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=< 9.1.1551
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
- Upstream crafted-archive proof of conceptproof of concept · demonstrated
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