Code execution via text-locked window exchange
Published Sep 5, 2023 · Updated Jun 23, 2026
Heap-based buffer overflow in Vim before 9.0.1873 allows local users to crash the editor or execute code through crafted input. During substitution, vim_regsub_both permits a window exchange while text is locked, invalidating buffer state and allowing a negative match count to drive an out-of-bounds heap access. Exploitation requires a user to process crafted input; successful abuse can terminate Vim or execute code in its process.
Summary
What happened
Heap-based buffer overflow in Vim before 9.0.1873 allows local users to crash the editor or execute code through crafted input. During substitution, vim_regsub_both permits a window exchange while text is locked, invalidating buffer state and allowing a negative match count to drive an out-of-bounds heap access. Exploitation requires a user to process crafted input; successful abuse can terminate Vim or execute code in its process.
The record
- CVE
- CVE-2023-4781
- Published
- Sep 5, 2023
- Updated
- Jun 23, 2026
- Vendor
- Vim
- Product
- Vim
- Classifications
- CWE-122, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 5, 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=unspecified <9.0.1873
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 vim_regsub_both crash proof of conceptproof 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