Quick answers
- Is CVE-2026-73077 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-73077 being exploited in the wild.
- How severe is CVE-2026-73077?
- Informational severity, with a CVSS score of 6.3, published 11 August 2026.
- Which products and versions are affected?
- Vim < 9.2.0839.
- Is there a fix for CVE-2026-73077?
- A patch was published on 2026-07-23: Vim 9.2.0839 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-73077 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-73077?
- Check whether you run Vim at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in runtime/ftplugin/sh.vim, runtime/ftplugin/zsh.vim, and runtime/ftplugin/ps1.vim, which define buffer-local keywordprg commands that pass Visual-mode selections directly to bash -c, zsh -c, or PowerShell -Command without proper shell metacharacter escaping. The fnameescape() function used by Vim's K command (in Normal mode) omits shell metacharacters like ;, &, (, ), and >, which are only stripped by SHELL_ESC_CHARS in non-Ex-command contexts. In Visual mode, K passes the entire selection verbatim rather than just the keyword, preserving shell metacharacters and allowing command injection. Exploitation requires the victim to deliberately select crafted text in Visual mode and invoke K; Normal-mode K is unaffected. The issue is fixed in Vim 9.2.0839.
Affected products
- Vim Vim < 9.2.0839
Timeline
- 2026-07-23: disclosed
- 2026-07-23: patched: Vim 9.2.0839 released
- 2026-08-11: advisory