CVE-2025-66476 is a high-severity uncontrolled search path vulnerability in Vim for Windows prior to 9.1.1947. When Vim is configured to use cmd.exe as its shell, external command resolution on Windows may search the current working directory before trusted system paths. As a result, when Vim invokes external utilities such as findstr.exe for :grep, shell commands via :!, filter commands using !, :make/compiler integrations, or other features that call external programs such as system(), it can execute a malicious executable planted in the directory associated with the edited file or current working directory. An attacker can place a trojanized binary with the expected name, such as findstr.exe, in a project folder and cause Vim to run it when the user edits files from that folder or changes into it. The flaw affects Vim for Windows 9.1.1946 and earlier and was fixed in 9.1.1947.
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.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability in Vim for Windows. Details not specified in the content.
A high-severity vulnerability in Vim for Windows that can lead to arbitrary code execution when interacting with compromised folders.
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.