Critical Security Flaw in vim Packages: Command Injection and Arbitrary Code Execution

vim-X11 Updated 13 Aug 2026

Summary

13/07/2026
N/A
Yes i
Unrated
Not published

ALSA-2026:38511: Important: vim security update. Affects vim-X11 versions < 2:8.2.2637-26.el9_8.10. Fixed in 2:8.2.2637-26.el9_8.10. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

Vim (Vi IMproved) is a highly popular text editor used for programming and general text editing. It enhances the traditional vi editor with additional features such as syntax highlighting, multi-level undo, and extensive plugin support. However, recent vulnerabilities have been identified that could allow attackers to execute arbitrary code or perform command injection through crafted inputs, particularly when handling .tgz archives and specific directory names.

Vulnerability Detail

The vulnerabilities in vim arise from improper handling of user inputs, leading to command injection and arbitrary code execution. Specifically, CVE-2026-46483 allows command injection when decompressing .tgz archives, while CVE-2026-47162 enables arbitrary code execution via crafted directory names. Additionally, CVE-2026-52858 and CVE-2026-47167 expose the editor to arbitrary code execution through Python omni-completion and crafted step-definition patterns, respectively. These vulnerabilities can be exploited by malicious users to execute harmful code on the system, potentially compromising sensitive data and system integrity.

How To Fix

Minimum fixed version

2:8.2.2637-26.el9_8.10

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 can avoid opening untrusted .tgz archives or refrain from using crafted directory names until the update is applied. Additionally, disabling Python omni-completion in vim may mitigate some risks associated with CVE-2026-52858.

Conclusion

The recent security update for vim addresses critical vulnerabilities that could lead to command injection and arbitrary code execution. Users are strongly advised to update their vim packages to the latest patched version to ensure their systems remain secure. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.

See every vulnerability recorded for vim-X11 →

Share this vulnerability

FAQ

Vim is an advanced text editor that is widely used for programming and text editing, offering features like syntax highlighting and plugin support.

The main vulnerabilities include command injection and arbitrary code execution through various methods, including .tgz archive handling and crafted directory names.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.

If you cannot update right away, avoid using untrusted archives and disable features like Python omni-completion to reduce risk.

For detailed information, refer to the CVE pages linked in the advisory or consult the official vim documentation.

Related vulnerabilities

Recent vulnerabilities recorded for vim-X11.

How To Fix

Minimum fixed version

2:8.2.2637-26.el9_8.10

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