Arbitrary code execution via Python omni-completion
Published Jun 11, 2026 · Updated Jun 11, 2026
Code injection in Vim before 9.2.0597 allows attackers to execute Python code through Python omni-completion in a hostile buffer. The python3complete.vim and pythoncomplete.vim scripts pass reconstructed definitions containing untrusted defaults, annotations, and class bases to exec(), which evaluates those expressions. Exploitation requires a build with Python support and a user to open the hostile buffer and invoke omni-completion; the code runs with that user's privileges.
Summary
What happened
Code injection in Vim before 9.2.0597 allows attackers to execute Python code through Python omni-completion in a hostile buffer. The python3complete.vim and pythoncomplete.vim scripts pass reconstructed definitions containing untrusted defaults, annotations, and class bases to exec(), which evaluates those expressions. Exploitation requires a build with Python support and a user to open the hostile buffer and invoke omni-completion; the code runs with that user's privileges.
The record
- CVE
- CVE-2026-52860
- Published
- Jun 11, 2026
- Updated
- Jun 11, 2026
- Vendor
- Vim
- Product
- Vim
- Classifications
- CWE-94, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 11, 2026CVE publishedPublication date reported by the CVE source.
- Jun 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 9.2.0597
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo