Critical Command Execution Vulnerability in Vim Package

vim Updated 01 May 2026

Summary

01/05/2026
N/A
Yes i
High
8.2

RLSA-2026:11389: Important: vim security update. Affects vim versions < 2:9.1.083-6.el10_1.4. Fixed in 2:9.1.083-6.el10_1.4. 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

Vim, short for Vi IMproved, is a highly configurable text editor built to enable efficient text editing. It is widely used by developers and system administrators for its powerful features and extensibility. However, a recent security vulnerability has been identified that allows arbitrary command execution through a bypass of the modeline sandbox, posing significant risks to users.

Vulnerability Detail

The vulnerability, identified as CVE-2026-34982, allows an attacker to execute arbitrary commands by exploiting a flaw in the modeline sandbox of Vim. This issue arises when the editor processes modelines, which are special lines in a file that can set editor options. If an attacker can manipulate these modelines, they can execute harmful commands, potentially leading to unauthorized access or data compromise. The CVSS score for this vulnerability is 8.2, indicating a high severity level.

How To Fix

Minimum fixed version

2:9.1.083-6.el10_1.4

This is the first release that contains the fix.

sudo dnf update vim

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

Workaround

As a temporary workaround, users can disable modelines in Vim by adding the following line to their Vim configuration file (usually located at ~/.vimrc): 'set nomodeline'. This will prevent Vim from executing any commands specified in modelines, thereby reducing the risk of exploitation until the package is updated.

Conclusion

The discovery of CVE-2026-34982 in the Vim package highlights a critical security risk that allows arbitrary command execution through modeline manipulation. Users are strongly advised to update their Vim installations to the patched version to protect against potential exploitation. Temporary workarounds are available, but updating is the most effective solution.

See every vulnerability recorded for vim →

Share this vulnerability

FAQ

CVE-2026-34982 is a security vulnerability in Vim that allows arbitrary command execution via a modeline sandbox bypass.

You can check if your Vim installation is affected by using the Vulert playground at Vulert Scanner, which allows you to monitor and alert for open-source vulnerabilities without requiring any signup.

Modelines are special lines in a file that allow users to set Vim options automatically when the file is opened. They can be a potential security risk if not handled properly.

If you cannot update Vim immediately, consider disabling modelines by adding 'set nomodeline' to your Vim configuration file to mitigate the risk temporarily.

The CVSS score for this vulnerability is 8.2, indicating a high severity level that requires prompt attention.

Related vulnerabilities

Recent vulnerabilities recorded for vim.

How To Fix

Minimum fixed version

2:9.1.083-6.el10_1.4

This is the first release that contains the fix.

sudo dnf update vim

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