Vim is an open source, command line text editor. Prior to version 9.2.0496, a code injection vulnerability exists in s:stepmatch() in the cucumber filetype plugin (runtime/ftplugin/cucumber.vim) on Vim builds with +ruby support. Step-definition patterns read from .rb files under the repository's features/*/ or stories/*/ directories are embedded into a Ruby Kernel.eval argument without sufficient escaping, allowing a crafted pattern in an attacker-controlled repository to execute arbitrary Ruby (and through it arbitrary shell commands) when the user invokes a step-jump mapping ([d, ]d). This issue has been patched in version 9.2.0496.
CVE-2026-47167
This medium-severity CVE scores 5.3 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 97% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 5.3
- EG Score
- 5.3(medium)
- EG Risk
- 24(Track)EG Risk 24/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity53% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 3%
- KEV
- Not listed
Published
June 11, 2026
Last Modified
June 15, 2026
Advisory Details (2)
Auto-updated Jun 14, 2026Vimscript Code Injection in cucumber filetype plugin via crafted step-definition regex affects Vim < 9.2.0496 · Advisory · vim/vim · GitHub
https://github.com/vim/vim/security/advisories/GHSA-4473-94jm-w5x9commit a65a52d684bc (vim/vim)
Fix landed in vim/vim commit a65a52d684bc — awaiting tagged release
https://github.com/vim/vim/commit/a65a52d684bc58535ad28a4ae824d22e76399934Vendor Advisories for CVE-2026-47167(9)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2026:68711Red Hat Product SecurityHigh
Red Hat Security Advisory: vim security update
- RHSA-2026:58981Red Hat Product SecurityCritical
Red Hat Security Advisory: Red Hat Update Infrastructure 5.3 Technology Preview security update
- RHSA-2026:54769Red Hat Product SecurityHigh
Red Hat Security Advisory: OpenShift Container Platform 4.22.10 bug fix and security update
- RHSA-2026:55431Red Hat Product SecurityHigh
Red Hat Security Advisory: vim security update
- RHSA-2026:53371Red Hat Product SecurityHigh
Red Hat Security Advisory: Insights proxy Container Image
- RHSA-2026:38511Red Hat Product SecurityHigh
Red Hat Security Advisory: vim security update
- RHSA-2026:38510Red Hat Product SecurityHigh
Red Hat Security Advisory: vim security update
- RHSA-2026:38509Red Hat Product SecurityHigh
Red Hat Security Advisory: vim security update
- +1 more
Patch Availability(8)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | xxd (2:9.1.0016-1ubuntu7.16) @ noble | 2026-09-14 | ubuntu |
| redhat | rhui5/rhua-tp-rhel9:1787241260 | 2026-08-24 | redhat |
| redhat | rhcos-4.22.9.8.202608130832-0 | 2026-08-18 | redhat |
| redhat | vim-2:9.1.083-5.el10_0.4 | 2026-08-17 | redhat |
| redhat | insights-proxy/insights-proxy-container-rhel9:1786433656 | 2026-08-11 | redhat |
| redhat | vim-2:8.2.2637-26.el9_8.10 | 2026-07-13 | redhat |
| redhat | vim-2:8.0.1763-27.el8_10 | 2026-07-13 | redhat |
| redhat | vim-2:9.1.083-9.el10_2.7 | 2026-07-13 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(4 across 4 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| vim | 2:8.2.2434-3 ... 2:9.2.0858-1 (63 versions) | — | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| vim | 2:9.0.1378-2 ... 2:9.2.0858-1 (45 versions) | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| vim | 2:9.1.1230-2 ... 2:9.2.0858-1 (19 versions) | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| vim | 2:9.1.1230-2 ... 2:9.2.0461-1 (16 versions) | 2:9.2.0524-1 | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Additional Vendor Advisories
(1)
Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.
Data Freshness Timeline
(refreshed 7× in last 7d / 34× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 187 total refreshes for this CVE.
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-14 04:09 UTCEG score recompute
- 2026-09-14 04:09 UTCVendor advisory
- 2026-09-13 16:47 UTCEPSS rescore
- 2026-09-12 15:01 UTCEPSS rescore
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 09:37 UTCEPSS rescore
- 2026-09-10 09:34 UTCEPSS rescore
- 2026-09-08 22:00 UTCEPSS rescore
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-02 14:12 UTCEPSS rescore
- 2026-09-01 13:54 UTCEPSS rescore
- 2026-08-31 00:03 UTCEG score recompute
- 2026-08-31 00:03 UTCVendor advisory
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 23:59 UTCEG score recompute
Show 75 moreShow fewer
- 2026-08-24 23:59 UTCVendor advisory
- 2026-08-23 10:41 UTCEG score recompute
- 2026-08-23 10:41 UTCVendor advisory
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 14:55 UTCEG score recompute
- 2026-08-21 14:55 UTCVendor advisory
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 17:06 UTCVendor advisory
- 2026-08-19 14:53 UTCEG score recompute
- 2026-08-19 14:53 UTCVendor advisory
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 23:03 UTCEG score recompute
- 2026-08-16 23:03 UTCVendor advisory
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 23:49 UTCEG score recompute
- 2026-08-15 23:49 UTCVendor advisory
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 22:39 UTCVendor advisory
- 2026-08-14 00:49 UTCEG score recompute
- 2026-08-14 00:49 UTCVendor advisory
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 02:59 UTCEG score recompute
- 2026-08-13 02:59 UTCVendor advisory
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-12 05:10 UTCEG score recompute
- 2026-08-12 05:10 UTCVendor advisory
- 2026-08-11 06:56 UTCEG score recompute
- 2026-08-11 06:56 UTCVendor advisory
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 09:06 UTCEG score recompute
- 2026-08-10 09:06 UTCVendor advisory
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 11:17 UTCEG score recompute
- 2026-08-09 11:17 UTCVendor advisory
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 13:27 UTCEG score recompute
- 2026-08-08 13:27 UTCVendor advisory
- 2026-08-07 15:37 UTCVendor advisory
- 2026-08-06 17:48 UTCEG score recompute
- 2026-08-06 17:48 UTCVendor advisory
- 2026-08-06 13:47 UTCEPSS rescore
- 2026-08-05 19:58 UTCEG score recompute
- 2026-08-05 19:58 UTCVendor advisory
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-04 15:50 UTCEG score recompute
- 2026-08-04 15:50 UTCVendor advisory
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 10:39 UTCEPSS rescore
- 2026-08-03 14:48 UTCEG score recompute
- 2026-08-03 14:48 UTCVendor advisory
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-02 07:20 UTCEG score recompute
- 2026-08-02 07:20 UTCVendor advisory
- 2026-08-02 02:27 UTCEPSS rescore
- 2026-08-01 09:30 UTCEG score recompute
- 2026-08-01 09:30 UTCVendor advisory
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-31 07:27 UTCEG score recompute
- 2026-07-31 07:27 UTCVendor advisory
- 2026-07-30 16:28 UTCEPSS rescore
- 2026-07-30 09:37 UTCEG score recompute
- 2026-07-30 09:37 UTCVendor advisory
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-29 04:47 UTCEG score recompute
- 2026-07-29 04:47 UTCVendor advisory
- 2026-07-28 15:37 UTCEPSS rescore
- 2026-07-27 18:38 UTCEG score recompute
- 2026-07-27 18:38 UTCVendor advisory
- 2026-07-26 20:48 UTCEG score recompute
- 2026-07-26 20:48 UTCVendor advisory
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-25 14:18 UTCEPSS rescore
Frequently asked(5)
What is CVE-2026-47167?
When was CVE-2026-47167 disclosed?
Is CVE-2026-47167 actively exploited?
What is the CVSS score of CVE-2026-47167?
How do I remediate CVE-2026-47167?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-47167
Is Your Infrastructure Affected by CVE-2026-47167?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.