Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
MediumPublic exploit

Heap Buffer Overflow in Vim spell file loading

IdentifiersCVE-2026-45130CWE-190· Integer Overflow or Wraparound

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.

Share:
For your environment

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.

ANALYST BRIEF

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.

The practical impact described in the provided content is denial of service via a crash of the Vim process caused by heap corruption during crafted spell file parsing. The underlying memory corruption is a heap buffer overflow, so successful exploitation provides an attacker with the ability to corrupt adjacent heap memory in the Vim process. The source material also notes possible code execution with sufficient heap grooming on 64-bit systems, but the advisory emphasizes process crash/DoS as the demonstrated and practical impact.

Mitigation

If you can’t patch tonight, do this now.

Until patched, reduce exposure by preventing untrusted .spl spell files from being placed on Vim's runtimepath, especially user-writable spell directories such as ~/.vim/spell/. Avoid loading untrusted spell files or enabling spell checking for attacker-controlled languages. Disable or restrict modeline processing where feasible, since a modeline can set spelllang and trigger spell file loading when a malicious spell file is already present on the runtimepath. Exercise caution when opening untrusted text files in environments where modelines are enabled.

Remediation

Patch, then assume compromise.

Upgrade Vim to version 9.2.0450 or later, which contains the patch for this issue. The provided content states the vulnerability was fixed in patch v9.2.0450.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

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.

VendorProductType
NeovimNeovimapplication
VimVimapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

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.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity4

Community discussion across Reddit, Mastodon, and other social sources.