Signal is active with 1 mentions in latest observed window
Immediate actions
Patch vim vim systems immediately
Recommended action window: Monitor and triage in normal cycle
NVD description
Vim is an open source, command line text editor. Prior to 9.2.0699, Vim's Python omni-completion (runtime/autoload/python3complete.vim and the legacy pythoncomplete.vim) executes reconstructed function and class definitions from the current buffer with exec() as part of populating the completion dictionary. When reconstructing that source, each scope's docstring is inserted verbatim between triple quotes with no escaping, so a hostile buffer can break out of the triple-quoted literal and execute attacker-controlled Python during omni-completion. This vulnerability is fixed in 9.2.0699.
🚨 HIGH - Vim Python omni-completion docstring exec() code injection (CVE-2026-57456)
Vim’s Python omni-completion scripts are vulnerable because they reconstruct function/class definitions from the current buffer and execute them via Python exec(), making the completion component itself the affected surface. The root cause is improper input sanitization/injection: docstrings are embedded verbatim into triple-quoted Python strings without escaping, enabling code injection. An attacker can exploit this by getting a developer to open or paste a crafted buffer/file and then trigger omni-completion, which causes the injected payload to execute under the user’s privileges. Impact is arbitrary code execution in the context of the Vim user, enabling data theft, persistence, or launching follow-on attacks from the workstation.
👉 Affected: vim < 9.2.0699 | Upgrade to 9.2.0699
Post summary
The post discloses a high‑severity Vim vulnerability that allows arbitrary code execution via code injection, and it provides a recommended patch by referencing the upgraded version.