Heap Buffer Overflow in Vim spell file loading
CVE-2026-45130 is a heap-based buffer overflow in Vim prior to 9.2.0450 in the spell file parsing logic, specifically read_compound() in src/spellfile.c. When Vim loads a crafted .spl spell file with UTF-8 encoding active, an attacker-controlled length field in the compound section is used in integer arithmetic on 32-bit signed int variables (including calculations such as todo * 2 + 7, with an additional todo * 2 in the UTF-8 path). This can overflow and wrap the computed allocation size to a small positive value, causing Vim to allocate an undersized heap buffer and then write beyond it in a loop that iterates based on the attacker-controlled length. The result is heap corruption during spell file loading. The issue is reachable when a malicious spell file is present on the runtimepath and Vim is induced to load it, including via spell checking for the matching language or a modeline that sets spelllang.
Are you exposed to this one?
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
Recent activity
5 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.