CVE-2026-51401: vim · CVE-2026-51401 is a high-severity
Affects vimSource CVE Database V5
Not known to be exploited · CVSS 7.7 High.
Data as of 26 Oct 2026, 09:16 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 4 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubvim/vimpkg:github/vim/vimOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Until an official fix is available, restrict local access to trusted users only and monitor for suspicious activity related to Vim usage. Avoid running untrusted code or scripts that could trigger this vulnerability.
Description
CVE-2026-51401 is a high-severity vulnerability in Vim Project versions 9.2.0389 and earlier. It allows a local attacker to execute arbitrary code via the vms_fixfilename() function in the source file vim/src/os_vms.c. The vulnerability is related to improper handling of input that leads to code execution without requiring user interaction or privileges. No official patch or remediation details are currently available.