Quick answers
- Is CVE-2026-55895 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-55895 being exploited in the wild.
- How severe is CVE-2026-55895?
- Informational severity, with a CVSS score of 5.7, published 25 June 2026.
- Which products and versions are affected?
- Vim < 9.2.0663.
- Is there a fix for CVE-2026-55895?
- A patch was published on 2026-06-16: Vim patch v9.2.0663 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-55895 attacked?
- It is attacked with local access, in a network appliance.
- Am I affected by CVE-2026-55895?
- Check whether you run Vim at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A Vimscript code injection vulnerability exists in the s:NetrwLocalRmFile() function within the netrw plugin (runtime/pack/dist/opt/netrw/autoload/netrw.vim). The root cause is insufficient sanitization of filenames before they are passed to the :execute command; specifically, only backslashes are escaped, while the pipe character (|) is not. An attacker can craft a filename containing a pipe character to terminate the intended 'bwipeout' command and execute arbitrary Vimscript or shell commands (via :! or system()). Exploitation requires the victim to browse a directory containing the malicious file using netrw and manually trigger the delete action (D mapping) on that specific file. The issue is resolved in Vim version 9.2.0663 by using fnameescape() for proper filename neutralization.
Affected products
- Vim Vim < 9.2.0663
Timeline
- 2026-06-16: patched: Vim patch v9.2.0663 released
- 2026-06-16: advisory: GitHub Security Advisory GHSA-vhh8-v6wx-hjjh published
- 2026-06-25: disclosed: NVD publication date