Arbitrary Code Execution in Vim Python Omni-Completion
CVE-2026-52860 is an arbitrary code execution vulnerability in Vim affecting versions prior to 9.2.0597. The flaw is in Vim's Python omni-completion implementation, including runtime/autoload/python3complete.vim and the legacy pythoncomplete.vim path, where source code reconstructed from the current Python buffer is executed with exec() to populate the completion dictionary. The reconstructed source includes function and class definitions derived from buffer contents; parameter lists, default expressions, annotations, and class base lists are preserved from attacker-controlled text harvested by internal parsing logic such as _parenparse(). Because Python evaluates function default values, parameter annotations, and class base expressions at definition time, a malicious Python buffer can cause attacker-controlled expressions to execute when omni-completion is triggered. The previously documented g:pythoncomplete_allow_import mitigation does not prevent this path because the executed content is not limited to harvested import/from statements.
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.
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.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
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.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
Recent activity
1 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.
The version that knows your environment.
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.