CVE-2026-51400
High · 8.4CVSS
8.4
EPSS
0.2%
Published
Aug 4, 2026
CISA due date
—
Cloudanix analysis
A problem in an older version of the Vim editor on certain computer systems lets someone already on the machine run any program they choose.
- Exploitation
- Local Privilege
- Attacker needs
- Local User
- Complexity
- Low
- Impact
- Full Compromise
- Component
- Application
- Class
- RCE
- Remediation
- Upgrade
- Effort
- Medium
- Patch risk
- Low
What it actually does
Allows local attackers to execute arbitrary code through a vulnerability in the vms_fixfilename() function in os_vms.c of Vim versions 9.2.0389 and earlier on VMS systems.
Why it matters to the business
Enables unauthorized code execution on affected systems, potentially leading to full system compromise without remote access or user interaction; stable low exploit likelihood reduces immediate urgency but unpatched instances remain exposed 82 days after disclosure.
How an attack unfolds
A local attacker on a VMS system invokes or manipulates the vulnerable vms_fixfilename function in Vim to inject and execute malicious code.
How to fix it
Upgrade Vim to a version newer than 9.2.0389 as soon as a fix is released by the Vim project; in the interim restrict local user access and avoid running Vim with elevated privileges on VMS systems.
How to confirm the fix worked
Confirm the installed Vim version exceeds 9.2.0389 and inspect os_vms.c for corrected vms_fixfilename implementation; test by attempting to trigger the function with boundary inputs.
Typical attack path
- Obtain local access to a VMS system running vulnerable Vim
- Locate the vulnerable Vim binary or source referencing os_vms.c
- Craft input that triggers vms_fixfilename with malicious payload
- Achieve arbitrary code execution with full privileges
How to detect it
Examine system logs for anomalous Vim process launches or unexpected code execution tied to VMS file name handling routines; review audit trails for unusual activity following Vim invocation.
What your security team should do
- Prioritize patching Vim on all VMS installations once fixed versions are available
- Limit local interactive access to systems hosting Vim
- Review and harden VMS file-handling permissions around editor processes
- Monitor EPSS and KEV updates for any rise in exploit activity
The record
An issue in Vim Project v9.2.0389 and earlier allows a local attacker to execute arbitrary code via the vms_fixfilename() function within file vim/src/os_vms.c
Affected packages
| Ecosystem | Package | Introduced | Fixed |
|---|
Related vulnerabilities
- CVE-2026-120678 A memory management flaw in the MongoDB C Driver's handling of compressed responses may… CWE-401
- CVE-2026-121512 Memory Leak with Amplification in µD3TN BPv6 EID Reference Handling allows… CWE-401
- CVE-2026-120440 QuickJS-NG before 0.16.0 contains a memory leak vulnerability in js_atomics_store() in… CWE-401
- CVE-2026-119286 GraphQL-core is a Python port of the GraphQL.js reference implementation. CWE-401
- CVE-2026-116157 ImageMagick before 7.1.2-33 contains a memory leak vulnerability in PerlMagick that fails… CWE-401
- CVE-2026-116158 ImageMagick before 7.1.2-33 contains a memory leak vulnerability in the magick compare… CWE-401
- CVE-2026-116159 ImageMagick before 6.9.13-58 and 7.x before 7.1.2-33 contains a memory leak in the… CWE-401
- CVE-2026-116156 ImageMagick before 6.9.13-58 and 7.x before 7.1.2-33 contains a memory leak caused by a… CWE-401