Vulnerability in vim - security update

vim Updated 02 Oct 2025

Summary

22/11/2016
N/A
Yes i
Unrated
Not published

DLA-718-1: vim - security update. Affects vim versions < 2:7.3.547-7+deb7u1. Fixed in 2:7.3.547-7+deb7u1. 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 is an enhanced vi editor that provides advanced features for text editing. It is widely used by developers and system administrators for various tasks. However, a security vulnerability has been discovered in vim that affects its handling of certain options. This vulnerability could allow an attacker to execute arbitrary code by exploiting a specially crafted modeline in a file.

Vulnerability Detail

The vulnerability in vim arises from a lack of proper validation of values for the filetype, syntax, and keymap options. When a file with a malicious modeline is opened, this flaw can be exploited to execute arbitrary code. This can have severe consequences, as an attacker could potentially gain unauthorized access to the system or perform malicious actions.

How To Fix

Minimum fixed version

2:7.3.547-7+deb7u1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade vim

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

Workaround

There is no known workaround for this vulnerability. It is essential to apply the security update as soon as possible to mitigate the risk of exploitation.

Conclusion

The vulnerability in vim can be mitigated by applying the recommended security update. It is crucial to promptly upgrade the vim package to protect against potential exploitation. For further assistance or information on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for vim →

Share this vulnerability

FAQ

Vim is an enhanced version of the vi editor, providing advanced features for text editing.

The vulnerability arises from a lack of proper validation of certain options in vim, allowing for the execution of arbitrary code.

A modeline is a special comment in a file that provides instructions or settings for the editor. In this case, a specially crafted modeline can trigger the vulnerability in vim.

Exploiting this vulnerability can lead to the execution of arbitrary code, which could result in unauthorized access to the system or malicious actions by an attacker.

To fix this vulnerability, you should upgrade the vim package to version 2:7.3.547-7+deb7u1 or later.

Related vulnerabilities

Recent vulnerabilities recorded for vim.

How To Fix

Minimum fixed version

2:7.3.547-7+deb7u1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade 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