Critical Security Update for vim and vim-common: CVE-2026-73073

vim-common Updated 06 Oct 2026

Summary

06/10/2026
N/A
Yes i
High
7.3

RHSA-2026:75769: Red Hat Security Advisory: vim security update. Affects vim-common versions < 2:9.1.083-9.el10_2.22. Fixed in 2:9.1.083-9.el10_2.22. 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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

vim is a highly configurable text editor built to enable efficient text editing. It is widely used in programming and system administration due to its powerful features and extensibility. The vim-common package provides shared files for the vim editor. The vulnerability identified as CVE-2026-73073 affects both vim and vim-common, potentially allowing unauthorized access to sensitive information.

Vulnerability Detail

The vulnerability CVE-2026-73073 arises from improper handling of certain input, which can lead to a buffer overflow. This flaw can be exploited by attackers to execute arbitrary code, potentially compromising the integrity and confidentiality of the system. The severity of this vulnerability is underscored by its CVSS score of 7.3, indicating a high risk to affected systems.

How To Fix

Minimum fixed version

2:9.1.083-9.el10_2.22

This is the first release that contains the fix.

sudo dnf update vim-common

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

Workaround

As a temporary measure, users can limit access to the vim editor or avoid using it until the update is applied. Additionally, consider using alternative text editors that are not affected by this vulnerability.

Conclusion

The vulnerability CVE-2026-73073 poses a significant risk to users of vim and vim-common. It is crucial to apply the necessary updates to protect your system from potential exploitation. Regular monitoring and timely updates are essential to maintaining software security.

See every vulnerability recorded for vim-common →

Share this vulnerability

FAQ

CVE-2026-73073 is a security vulnerability in the vim and vim-common packages that can lead to arbitrary code execution due to improper input handling.

You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.

The CVSS score for CVE-2026-73073 is 7.3, indicating a high severity level.

If immediate updates are not possible, consider using alternative text editors and restrict access to vim until the vulnerability is patched.

Related vulnerabilities

Recent vulnerabilities recorded for vim-common.

How To Fix

Minimum fixed version

2:9.1.083-9.el10_2.22

This is the first release that contains the fix.

sudo dnf update vim-common

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