CVE-2026-47167

MEDIUMNVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

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).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 5.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
24
EG Risk 24/100

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 computed
Severity53% × 45%
Exploitation0% × 40%
Automatability0% × 15%
EPSS PROB
0.1%
EPSS %ILE
2nd
KEV
Not listed

Published

June 11, 2026

Last Modified

June 15, 2026

Advisory Details (2)

Auto-updated Jun 14, 2026
Patch available. Sources: github_commit, github.
github Patch Available

Vimscript 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-w5x9
github_commit

commit a65a52d684bc (vim/vim)

Fix landed in vim/vim commit a65a52d684bc — awaiting tagged release

https://github.com/vim/vim/commit/a65a52d684bc58535ad28a4ae824d22e76399934

Vendor Advisories for CVE-2026-47167(20)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(8)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntuxxd (2:9.1.0016-1ubuntu7.16) @ noble2026-09-14ubuntu
redhatrhui5/rhua-tp-rhel9:17872412602026-08-24redhat
redhatrhcos-4.22.9.8.202608130832-02026-08-18redhat
redhatvim-2:9.1.083-5.el10_0.42026-08-17redhat
redhatinsights-proxy/insights-proxy-container-rhel9:17864336562026-08-11redhat
redhatvim-2:8.2.2637-26.el9_8.102026-07-13redhat
redhatvim-2:8.0.1763-27.el8_102026-07-13redhat
redhatvim-2:9.1.083-9.el10_2.72026-07-13redhat

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)
PackageVulnerable rangeFix by version rangeDependents
vim2:8.2.2434-3 ... 2:9.2.0858-1 (63 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
vim2:9.0.1378-2 ... 2:9.2.0858-1 (45 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
vim2:9.1.1230-2 ... 2:9.2.0858-1 (19 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
vim2:9.1.1230-2 ... 2:9.2.0461-1 (16 versions)
  • every version up to 2:9.2.0524-1: fixed in 2:9.2.0524-1
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(9)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 6× in last 7d / 24× 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 198 total refreshes for this CVE.

  1. 2026-10-04 23:22 UTCEPSS rescore
  2. 2026-10-03 14:25 UTCEPSS rescore
  3. 2026-10-03 08:39 UTCOSV refresh
  4. 2026-10-01 19:50 UTCEPSS rescore
  5. 2026-09-30 15:03 UTCEPSS rescore
  6. 2026-09-28 13:51 UTCEPSS rescore
  7. 2026-09-27 13:48 UTCEPSS rescore
  8. 2026-09-26 15:59 UTCEPSS rescore
  9. 2026-09-26 00:27 UTCEPSS rescore
  10. 2026-09-23 17:53 UTCEPSS rescore
  11. 2026-09-20 20:16 UTCEPSS rescore
  12. 2026-09-18 19:28 UTCEPSS rescore
  13. 2026-09-16 14:08 UTCEPSS rescore
  14. 2026-09-16 05:15 UTCEPSS rescore
  15. 2026-09-14 04:09 UTCEG score recompute
  16. 2026-09-14 04:09 UTCVendor advisory
  17. 2026-09-13 16:47 UTCEPSS rescore
  18. 2026-09-12 15:01 UTCEPSS rescore
  19. 2026-09-11 14:53 UTCEPSS rescore
  20. 2026-09-11 09:37 UTCEPSS rescore
  21. 2026-09-10 09:34 UTCEPSS rescore
  22. 2026-09-08 22:00 UTCEPSS rescore
  23. 2026-09-07 16:01 UTCEPSS rescore
  24. 2026-09-06 13:47 UTCEPSS rescore
  25. 2026-09-04 05:06 UTCEPSS rescore
Show 75 more
  1. 2026-09-02 14:12 UTCEPSS rescore
  2. 2026-09-01 13:54 UTCEPSS rescore
  3. 2026-08-31 00:03 UTCEG score recompute
  4. 2026-08-31 00:03 UTCVendor advisory
  5. 2026-08-30 19:17 UTCEPSS rescore
  6. 2026-08-30 01:22 UTCEPSS rescore
  7. 2026-08-28 21:41 UTCEPSS rescore
  8. 2026-08-27 14:25 UTCEPSS rescore
  9. 2026-08-26 14:46 UTCEPSS rescore
  10. 2026-08-25 13:49 UTCEPSS rescore
  11. 2026-08-24 23:59 UTCEG score recompute
  12. 2026-08-24 23:59 UTCVendor advisory
  13. 2026-08-23 10:41 UTCEG score recompute
  14. 2026-08-23 10:41 UTCVendor advisory
  15. 2026-08-23 00:19 UTCEPSS rescore
  16. 2026-08-21 23:49 UTCEPSS rescore
  17. 2026-08-21 14:55 UTCEG score recompute
  18. 2026-08-21 14:55 UTCVendor advisory
  19. 2026-08-20 22:55 UTCEPSS rescore
  20. 2026-08-20 17:06 UTCVendor advisory
  21. 2026-08-19 14:53 UTCEG score recompute
  22. 2026-08-19 14:53 UTCVendor advisory
  23. 2026-08-18 13:48 UTCEPSS rescore
  24. 2026-08-17 13:47 UTCEPSS rescore
  25. 2026-08-16 23:03 UTCEG score recompute
  26. 2026-08-16 23:03 UTCVendor advisory
  27. 2026-08-16 14:56 UTCEPSS rescore
  28. 2026-08-16 02:14 UTCEPSS rescore
  29. 2026-08-15 23:49 UTCEG score recompute
  30. 2026-08-15 23:49 UTCVendor advisory
  31. 2026-08-15 01:30 UTCEPSS rescore
  32. 2026-08-14 22:39 UTCVendor advisory
  33. 2026-08-14 00:49 UTCEG score recompute
  34. 2026-08-14 00:49 UTCVendor advisory
  35. 2026-08-13 22:00 UTCEPSS rescore
  36. 2026-08-13 02:59 UTCEG score recompute
  37. 2026-08-13 02:59 UTCVendor advisory
  38. 2026-08-12 13:51 UTCEPSS rescore
  39. 2026-08-12 05:10 UTCEG score recompute
  40. 2026-08-12 05:10 UTCVendor advisory
  41. 2026-08-11 06:56 UTCEG score recompute
  42. 2026-08-11 06:56 UTCVendor advisory
  43. 2026-08-11 00:00 UTCEPSS rescore
  44. 2026-08-10 09:06 UTCEG score recompute
  45. 2026-08-10 09:06 UTCVendor advisory
  46. 2026-08-09 13:46 UTCEPSS rescore
  47. 2026-08-09 11:17 UTCEG score recompute
  48. 2026-08-09 11:17 UTCVendor advisory
  49. 2026-08-08 16:37 UTCEPSS rescore
  50. 2026-08-08 13:27 UTCEG score recompute
  51. 2026-08-08 13:27 UTCVendor advisory
  52. 2026-08-07 15:37 UTCVendor advisory
  53. 2026-08-06 17:48 UTCEG score recompute
  54. 2026-08-06 17:48 UTCVendor advisory
  55. 2026-08-06 13:47 UTCEPSS rescore
  56. 2026-08-05 19:58 UTCEG score recompute
  57. 2026-08-05 19:58 UTCVendor advisory
  58. 2026-08-05 19:17 UTCEPSS rescore
  59. 2026-08-04 15:50 UTCEG score recompute
  60. 2026-08-04 15:50 UTCVendor advisory
  61. 2026-08-04 15:10 UTCEPSS rescore
  62. 2026-08-04 10:39 UTCEPSS rescore
  63. 2026-08-03 14:48 UTCEG score recompute
  64. 2026-08-03 14:48 UTCVendor advisory
  65. 2026-08-03 10:36 UTCEPSS rescore
  66. 2026-08-02 07:20 UTCEG score recompute
  67. 2026-08-02 07:20 UTCVendor advisory
  68. 2026-08-02 02:27 UTCEPSS rescore
  69. 2026-08-01 09:30 UTCEG score recompute
  70. 2026-08-01 09:30 UTCVendor advisory
  71. 2026-08-01 04:16 UTCEPSS rescore
  72. 2026-07-31 07:27 UTCEG score recompute
  73. 2026-07-31 07:27 UTCVendor advisory
  74. 2026-07-30 16:28 UTCEPSS rescore
  75. 2026-07-30 09:37 UTCEG score recompute

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-47167?
CVE-2026-47167 is a medium vulnerability published on June 11, 2026. 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…
When was CVE-2026-47167 disclosed?
CVE-2026-47167 was first published on June 11, 2026, with the most recent update on June 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47167 actively exploited?
CVE-2026-47167 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-47167?
CVE-2026-47167 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-47167?
A fix for CVE-2026-47167 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-47167 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-47167

Explore →

Is Your Infrastructure Affected by CVE-2026-47167?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs