Application crash via freed window dereference
Published Nov 16, 2023 · Updated Jun 23, 2026
Use-after-free in win_close() in Vim before 9.0.2106 allows local users to crash the editor by closing a crafted window. A window-closing autocommand can free the current window structure before win_close() sets its w_closing member, leaving win_close() to dereference stale memory. Triggering requires a local user to run crafted Vim commands and interact with the editor; upstream demonstrated only an application crash, not payload execution.
Summary
What happened
Use-after-free in win_close() in Vim before 9.0.2106 allows local users to crash the editor by closing a crafted window. A window-closing autocommand can free the current window structure before win_close() sets its w_closing member, leaving win_close() to dereference stale memory. Triggering requires a local user to run crafted Vim commands and interact with the editor; upstream demonstrated only an application crash, not payload execution.
The record
- CVE
- CVE-2023-48231
- Published
- Nov 16, 2023
- Updated
- Jun 23, 2026
- Vendor
- Vim
- Product
- Vim
- Classifications
- CWE-416, T1204.002
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 16, 2023CVE publishedPublication date reported by the CVE source.
- Jun 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 9.0.2106
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- Upstream win_close crash regression inputproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo