Code execution via unescaped omni-completion docstrings
Published Jun 25, 2026 · Updated Jun 25, 2026
Code injection in Vim before 9.2.0699 allows context-dependent attackers to execute Python code through a hostile buffer's docstring. The get_code() methods insert buffer-derived docstrings unescaped between triple quotes before passing reconstructed definitions to exec(). Execution requires Vim with +python3 or +python, a hostile Python buffer, and triggered omni-completion; code runs with the local user's privileges.
Summary
What happened
Code injection in Vim before 9.2.0699 allows context-dependent attackers to execute Python code through a hostile buffer's docstring. The get_code() methods insert buffer-derived docstrings unescaped between triple quotes before passing reconstructed definitions to exec(). Execution requires Vim with +python3 or +python, a hostile Python buffer, and triggered omni-completion; code runs with the local user's privileges.
The record
- CVE
- CVE-2026-57456
- Published
- Jun 25, 2026
- Updated
- Jun 25, 2026
- Vendor
- Vim
- Product
- Vim
- Classifications
- CWE-94, T1204.002, T1059.006
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 25, 2026CVE publishedPublication date reported by the CVE source.
- Jun 25, 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.0699
What conditions does exploitation require?
What is affected?
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
- Upstream malicious docstring regression-test payloadproof of concept · demonstrated
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