cucumber filetype plugin · Vim: Vimscript Code Injection
Affects MicrosoftSource GCVE Database
Not known to be exploited.
Data as of 29 Oct 2026, 19:04 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Exploitation evidence
Disclosed: evidence found.
CVE published 2 Jun 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 29 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Security Response Center Microsoft | Affected
| Fixed in– |
AI-suggested
Until an official fix is available, users should avoid opening untrusted cucumber files or step-definition regexes in Vim. Monitor official Microsoft Security Response Center advisories for updates.
Description
A vulnerability in the Vim text editor's cucumber filetype plugin allows for Vimscript code injection via a crafted step-definition regular expression. This issue is identified as CVE-2026-47167 and is related to improper handling of input in the plugin, leading to potential code execution within Vim. No CVSS score is provided, and no public exploit or patch information is currently available.