CVE-2025-55157
BaseFortify
Publication date: 2025-08-11
Last updated on: 2025-08-12
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| vim | vim | From 9.1.1231 (inc) to 9.1.1400 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-416 | The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in Vim occurs when processing nested tuples in Vim script. An error during evaluation can cause a use-after-free condition in Vim's internal tuple reference management, specifically in the tuple_unref() function. This function may access memory that has already been freed due to improper handling of the tuple's lifetime, leading to memory corruption. Exploiting this requires the user to explicitly execute a crafted script within Vim. The issue has been fixed in version 9.1.1400.
How can this vulnerability impact me? :
The vulnerability can lead to memory corruption within Vim, which may cause the application to crash or behave unpredictably. In some cases, this could potentially be exploited to execute arbitrary code or escalate privileges, depending on the context and environment. However, exploitation requires direct user interaction by running a malicious Vim script.
What immediate steps should I take to mitigate this vulnerability?
Update Vim to version 9.1.1400 or later, as this version contains the patch that fixes the use-after-free vulnerability in tuple_unref(). Avoid executing untrusted Vim scripts to prevent exploitation.