Skip to main content
CVE-2026-52860VulnerabilityPublished Updated

Microsoft · Vim: Arbitrary Code Execution via Python Omni-Completion

Affects MicrosoftSource GCVE Database

0
Compare

Not known to be exploited.

Data as of 30 Oct 2026, 06:59 UTC

Severity
High

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS
0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Microsoft Security Response Center MicrosoftAffected
  • =3.0
Fixed in–

AI-suggested

Until an official fix is available, users should consider disabling Python omni-completion in Vim if feasible or avoid opening untrusted files that could trigger this feature.

Description

A vulnerability identified as CVE-2026-52860 affects Vim, specifically involving arbitrary code execution via Python omni-completion. The vulnerability is related to improper handling of code execution within Vim's Python integration. No CVSS score is provided, and no known exploits are reported in the wild. No patch or remediation details are currently available.

References

Community reviews

Loading reviews…