CVE-2026-41411: vim · OS Command Injection
Affects vimSource GCVE Database
Not known to be exploited · CVSS 6.6 Medium : upgrade to 9.2.0357 when convenient.
Data as of 12 Nov 2026, 01:05 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 6.6 |
|---|
- Patch
- Available – fixed in 9.2.0357
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:LExploitation evidence
Disclosed: evidence found.
CVE published 24 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.
What to do
Upgrade vim to 9.2.0357.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| vim vim | Affected
| Fixed in
|
AI-suggested
Upgrade Vim to version 9.2.0357 or later, where this vulnerability is fixed. No other mitigation is indicated by the vendor advisory. Users should apply this official fix to prevent exploitation.
Description
CVE-2026-41411 is a command injection vulnerability in Vim prior to version 9.2.0357. The flaw exists in Vim's tag file processing where the filename field is passed through wildcard expansion, allowing execution of embedded commands via backtick syntax with the privileges of the running user.