Crash via tagfunc-triggered window closure
Published Sep 6, 2022 · Updated Nov 3, 2025
Use-after-free in Vim before 9.0.0389 allows local users to crash the editor through a tag function that closes its window. The do_tag function retains the current tag stack across a tagfunc callback, then continues using that stale structure after the callback closes and frees the active window. The trigger requires interaction with a crafted Vim script or configuration and a tag lookup; the upstream patch documents an editor crash.
Summary
What happened
Use-after-free in Vim before 9.0.0389 allows local users to crash the editor through a tag function that closes its window. The do_tag function retains the current tag stack across a tagfunc callback, then continues using that stale structure after the callback closes and frees the active window. The trigger requires interaction with a crafted Vim script or configuration and a tag lookup; the upstream patch documents an editor crash.
The record
- CVE
- CVE-2022-3134
- Published
- Sep 6, 2022
- Updated
- Nov 3, 2025
- Vendor
- Vim
- Product
- Vim
- Classifications
- CWE-416, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 6, 2022CVE publishedPublication date reported by the CVE source.
- Nov 3, 2025Record 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=unspecified <9.0.0389
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
- huntr.dev tagfunc window-closure proof of conceptproof of concept · unverified
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