CVE-2026-51400
Local arbitrary code execution in Vim via vms_fixfilename() (v9.2.0389 and earlier).
Is CVE-2026-51400 being exploited?
Not confirmed. CVE-2026-51400 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.12% probability of exploitation in the next 30 days.
How severe is CVE-2026-51400?
CVE-2026-51400 is rated High with a CVSS score of 8.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-51400?
Not known from our data. No patch reference has been recorded for CVE-2026-51400, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-51400 affect?
CVE-2026-51400 affects Vim <= 9.2.0389, Vim builds using src/os_vms.c (VMS builds). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-51400?
Patch Vim when vendor fix released; restrict untrusted file access and limit local user privileges.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Local attacker can execute arbitrary code as the user running Vim by exploiting vms_fixfilename(), enabling system compromise or persistence.
Immediate action required