Vim versions prior to 9.2.0561 contain an arbitrary code execution vulnerability in Python omni-completion. With the Python 3 interpreter enabled, or the legacy Python interpreter enabled for the corresponding completion implementation, the completion script executes import and from statements from the current buffer through Python's import machinery. Because the buffer's working directory is included in Python's module search path, opening a malicious Python file accompanied by a sibling Python package and invoking omni-completion executes the package's top-level code with the editing user's privileges.
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.
23 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability covered by Huawei EulerOS advisory EulerOS_SA-2026-4295 for Vim packages. The excerpt does not describe its technical cause or individual impact.
A vulnerability covered by the Huawei EulerOS Vim security update. Individual technical details are not provided.
A vulnerability covered by the EulerOS Vim security check. Specific flaw details and impacts are not provided.
A vulnerability covered by the EulerOS Vim security update; its underlying flaw and individual exploit availability are not described.
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.