Critical Security Flaw in vim Packages: Arbitrary Command Execution Vulnerability

vim-X11 Updated 07 Oct 2026

Summary

05/10/2026
N/A
Yes i
Unrated
Not published

ALSA-2026:75768: Important: vim security update. Affects vim-X11 versions < 2:8.2.2637-26.el9_8.23. Fixed in 2:8.2.2637-26.el9_8.23. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Vim (Vi IMproved) is a highly popular text editor that enhances the traditional vi editor with additional features and improvements. It is widely used for programming and text editing due to its efficiency and versatility. However, a recent security issue has been identified that allows for arbitrary command execution through a crafted tags file during C omni-completion, posing a significant risk to users.

Vulnerability Detail

The vulnerability, identified as CVE-2026-73073, arises from improper handling of crafted tags files in Vim's C omni-completion feature. This flaw can be exploited by an attacker to execute arbitrary commands on the system where Vim is running. The implications of this vulnerability are severe, as it could lead to unauthorized access, data breaches, or system compromise, especially in environments where Vim is used for sensitive tasks.

How To Fix

Minimum fixed version

2:8.2.2637-26.el9_8.23

This is the first release that contains the fix.

sudo dnf update vim-X11

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a temporary workaround, users are advised to avoid using the C omni-completion feature in Vim until the package is updated to the fixed version. Additionally, users can restrict access to Vim in environments where the risk of exploitation is high.

Conclusion

The identified vulnerability in Vim poses a significant risk to users, allowing for arbitrary command execution through crafted tags files. It is crucial for users to update their packages to the patched version to ensure their systems remain secure. Awareness and prompt action are essential in mitigating the risks associated with this vulnerability.

See every vulnerability recorded for vim-X11 →

Share this vulnerability

FAQ

CVE-2026-73073 is a security vulnerability in Vim that allows for arbitrary command execution via crafted tags files during C omni-completion.

You can check if your version of Vim is affected by using tools like Vulert, which monitors open-source vulnerabilities in your software.

The risks include unauthorized command execution, potential data breaches, and system compromise, especially in sensitive environments.

Yes, a patch is available. Users should update to version 2:8.2.2637-26.el9_8.23 to mitigate the vulnerability.

You can update your Vim packages by running the command 'sudo dnf update vim-X11 vim-common vim-enhanced vim-filesystem vim-minimal' in your terminal.

Related vulnerabilities

Recent vulnerabilities recorded for vim-X11.

How To Fix

Minimum fixed version

2:8.2.2637-26.el9_8.23

This is the first release that contains the fix.

sudo dnf update vim-X11

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback