Cloudanix VulnDB

CVE-2026-51401

High · 7.7

CVSS

7.7

EPSS

0.2%

Published

Aug 4, 2026

CISA due date

—

Cloudanix analysis

Monitor only SSVC: Track

A bug in the Vim editor on certain older computer systems lets someone who already has access to the machine run their own programs without extra permission.

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

The flaw permits local arbitrary code execution through improper handling in the vms_fixfilename() function in vim/src/os_vms.c on VMS platforms, allowing crafted filename input to hijack control flow.

Why it matters to the business

Local attackers can run unauthorized code on affected systems, risking data theft, persistence, or disruption on VMS environments where Vim is installed.

How an attack unfolds

A local attacker supplies malicious input to Vim that reaches vms_fixfilename(), triggering code execution without authentication or user interaction due to the low-complexity local vector.

How to fix it

Upgrade Vim beyond version 9.2.0389 once a fix is released by the project; in the interim restrict execution of Vim on VMS systems and apply compensating controls such as mandatory access controls around the binary.

How to confirm the fix worked

Confirm Vim versions are newer than 9.2.0389, review source for sanitized handling in os_vms.c, and test with known-malicious filename patterns to ensure no code execution occurs.

Typical attack path

  1. Obtain local shell or process execution rights on the target VMS system
  2. Invoke Vim or a dependent tool with a crafted filename argument
  3. Trigger vms_fixfilename() to achieve arbitrary code execution

How to detect it

Review process creation logs and command-line histories for Vim invocations containing unusual or overly long filenames; inspect for unexpected child processes spawned from Vim on VMS hosts.

What your security team should do

  • Prioritize patching Vim on all VMS hosts as soon as a fixed release is available
  • Limit local user privileges and Vim usage to only required accounts
  • Add runtime protections such as seccomp or equivalent sandboxing around text editors

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