Memory corruption via multibyte statusline fill
Published Feb 27, 2026 · Updated Feb 27, 2026
Stack-based buffer overflow in Vim before 9.2.0078 allows local users to corrupt memory via a crafted statusline on a wide terminal. The build_stl_str_hl() size check counts remaining screen cells instead of the multibyte fill character's byte length, allowing its fill loop to overrun the 4096-byte MAXPATHL stack buffer. Triggering requires influence over fillchars or statusline settings, such as through a malicious modeline or plugin, and a terminal wider than about 1,365 columns.
Summary
What happened
Stack-based buffer overflow in Vim before 9.2.0078 allows local users to corrupt memory via a crafted statusline on a wide terminal. The build_stl_str_hl() size check counts remaining screen cells instead of the multibyte fill character's byte length, allowing its fill loop to overrun the 4096-byte MAXPATHL stack buffer. Triggering requires influence over fillchars or statusline settings, such as through a malicious modeline or plugin, and a terminal wider than about 1,365 columns.
The record
- CVE
- CVE-2026-28422
- Published
- Feb 27, 2026
- Updated
- Feb 27, 2026
- Vendor
- Vim
- Product
- Vim
- Classifications
- CWE-121, T1204.002
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 27, 2026CVE publishedPublication date reported by the CVE source.
- Feb 27, 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.2.0078
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
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