Loading vulnerability…
CVE-2026-55693 is a stack-based out-of-bounds write vulnerability in Vim prior to version 9.2.0653. The flaw is in the tree_count_words() function in src/spellfile.c, which populates word-count fields for a spell-file word trie using an iterative traversal with a depth counter. That counter is constrained only by the structure of the trie and is not validated against the bounds of fixed-size MAXWLEN stack arrays used as traversal state, including arridx[], curi[], and wordcount[]. A crafted spell dictionary file pair can cause traversal to descend beyond the capacity of those arrays during spell suggestion processing, resulting in writes past the end of stack buffers. This corrupts the stack frame and causes the editor to crash.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
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.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A specific vulnerability referenced in a Miracle Linux advisory affecting Vim-related packages; no further technical details are provided in the content.
An out-of-bounds write vulnerability in Vim's spell file word count handling.
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.