Loading vulnerability…
CVE-2026-28421 affects Vim versions prior to 9.2.0077 and resides in the editor’s swap file recovery logic, particularly the recovery path in ml_recover(). The vulnerability is caused by insufficient validation of fields read from crafted pointer blocks in a swap file, including block numbers and related metadata. Two related failure modes are described: a heap-based buffer overflow and a separate segmentation fault condition. In the overflow case, crafted pointer block values can cause recovery operations to repeatedly append placeholder recovery text, eventually overrunning an internal array associated with the current data block. In the crash case, negative or otherwise invalid block metadata can propagate into file-reading operations with unvalidated offsets and counts, leading to invalid memory access. The issue is triggered when Vim attempts recovery from a maliciously crafted swap file.
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.
9 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.
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.