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
Trending — Patch released this week
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 0

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.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 computed
Severity53% × 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, 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(7)

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

Patch Availability(7)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuxxd (2:8.2.3995-1ubuntu2.32) @ jammy2026-08-20ubuntu
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.0.1763-27.el8_102026-07-13redhat
redhatvim-2:8.2.2637-26.el9_8.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 rangeFixed inDependents
vim2:8.2.2434-3 ... 2:9.2.0858-1 (63 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
vim2:9.0.1378-2 ... 2:9.2.0858-1 (45 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
vim2:9.1.1230-2 ... 2:9.2.0858-1 (19 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
vim2: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 14× in last 7d / 72× 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 155 total refreshes for this CVE.

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

Related CVEs(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 in the National Vulnerability Database 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% probability of exploitation in the next 30 days, which ranks it in the top 96.5% of all 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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47167, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs