Use After Free Vulnerability in vim/vim

vim Updated 02 Oct 2025

Summary

02/02/2022
N/A
Yes i
High
7.8

CVE-2022-0443: Use After Free in GitHub repository vim/vim prior to 8.2. Affects vim versions < 8.2.4619-r0. Fixed in 8.2.4619-r0. 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 popular text editor that is widely used in various operating systems. It provides powerful features for editing and manipulating text files. However, a vulnerability has been discovered in the GitHub repository vim/vim prior to version 8.2. This vulnerability allows for a use after free scenario, which can lead to potential security risks.

Vulnerability Detail

The use after free vulnerability in vim/vim arises when a program attempts to access memory that has already been freed. This can result in the execution of arbitrary code or a crash of the application. In the case of vim/vim, this vulnerability can be exploited by an attacker to gain unauthorized access or perform other malicious activities on the affected system. The severity of this vulnerability is rated as high, with a CVSS score of 7.8.

How To Fix

Minimum fixed version

8.2.4619-r0

This is the first release that contains the fix.

sudo apk add --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 recommended fix by updating the vim/vim package to the latest version.

Conclusion

The use after free vulnerability in vim/vim can pose significant security risks. It is crucial to update the package to the latest version to mitigate these risks. For further assistance and support in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for vim →

Share this vulnerability

FAQ

vim is a text editor that is widely used for editing and manipulating text files. It provides powerful features and is available for various operating systems.

A use after free vulnerability occurs when a program attempts to access memory that has already been freed. This can lead to the execution of arbitrary code or a crash of the application.

This vulnerability can be exploited by an attacker to gain unauthorized access or perform other malicious activities on the affected system.

The severity of this vulnerability is rated as high, with a CVSS score of 7.8.

To fix this vulnerability, it is recommended to update the vim/vim package to version 8.2.4619-r0 or later.

Related vulnerabilities

Recent vulnerabilities recorded for vim.

How To Fix

Minimum fixed version

8.2.4619-r0

This is the first release that contains the fix.

sudo apk add --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