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 — 3 sources updated this week
5.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.3Exploit: NoneExposed: 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
3.4%
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(1)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuxxd (2:9.1.0967-1ubuntu6.7) @ questing2026-07-16ubuntu

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.

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 9× in last 7d / 57× 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.

  1. 2026-07-23 03:17 UTCEG score recompute
  2. 2026-07-22 14:08 UTCEPSS rescore
  3. 2026-07-21 15:24 UTCEPSS rescore
  4. 2026-07-20 17:08 UTCEPSS rescore
  5. 2026-07-19 14:31 UTCEPSS rescore
  6. 2026-07-19 02:29 UTCEPSS rescore
  7. 2026-07-18 10:04 UTCEPSS rescore
  8. 2026-07-16 23:27 UTCVendor advisory
  9. 2026-07-16 17:03 UTCEPSS rescore
  10. 2026-07-15 16:57 UTCEPSS rescore
  11. 2026-07-15 16:28 UTCVendor advisory
  12. 2026-07-15 02:00 UTCEPSS rescore
  13. 2026-07-14 17:05 UTCVendor advisory
  14. 2026-07-13 22:30 UTCEPSS rescore
  15. 2026-07-13 19:16 UTCVendor advisory
  16. 2026-07-12 19:49 UTCVendor advisory
  17. 2026-07-12 05:46 UTCEPSS rescore
  18. 2026-07-11 18:05 UTCVendor advisory
  19. 2026-07-11 08:27 UTCEPSS rescore
  20. 2026-07-10 20:14 UTCVendor advisory
  21. 2026-07-09 22:20 UTCVendor advisory
  22. 2026-07-09 19:10 UTCEPSS rescore
  23. 2026-07-08 21:24 UTCVendor advisory
  24. 2026-07-08 15:16 UTCEPSS rescore
  25. 2026-07-07 23:35 UTCVendor advisory
Show 60 more
  1. 2026-07-07 13:46 UTCEPSS rescore
  2. 2026-07-07 01:44 UTCVendor advisory
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-05 19:35 UTCVendor advisory
  6. 2026-07-05 02:30 UTCEPSS rescore
  7. 2026-07-04 21:41 UTCVendor advisory
  8. 2026-07-04 06:31 UTCEPSS rescore
  9. 2026-07-03 23:21 UTCVendor advisory
  10. 2026-07-03 01:20 UTCVendor advisory
  11. 2026-07-02 03:24 UTCVendor advisory
  12. 2026-07-01 15:07 UTCEPSS rescore
  13. 2026-07-01 05:35 UTCVendor advisory
  14. 2026-06-30 23:22 UTCEPSS rescore
  15. 2026-06-30 07:44 UTCVendor advisory
  16. 2026-06-29 14:06 UTCEPSS rescore
  17. 2026-06-29 14:06 UTCEPSS rescore
  18. 2026-06-29 09:54 UTCVendor advisory
  19. 2026-06-28 14:07 UTCEPSS rescore
  20. 2026-06-28 12:04 UTCVendor advisory
  21. 2026-06-28 04:56 UTCEPSS rescore
  22. 2026-06-28 04:56 UTCEPSS rescore
  23. 2026-06-27 14:14 UTCVendor advisory
  24. 2026-06-27 03:08 UTCEPSS rescore
  25. 2026-06-26 16:24 UTCVendor advisory
  26. 2026-06-25 18:34 UTCVendor advisory
  27. 2026-06-25 13:49 UTCEPSS rescore
  28. 2026-06-24 20:44 UTCVendor advisory
  29. 2026-06-24 14:05 UTCEPSS rescore
  30. 2026-06-23 21:33 UTCEPSS rescore
  31. 2026-06-23 21:33 UTCEPSS rescore
  32. 2026-06-23 19:43 UTCVendor advisory
  33. 2026-06-22 21:54 UTCVendor advisory
  34. 2026-06-22 14:25 UTCEPSS rescore
  35. 2026-06-22 14:25 UTCEPSS rescore
  36. 2026-06-21 23:52 UTCVendor advisory
  37. 2026-06-21 14:56 UTCEPSS rescore
  38. 2026-06-21 14:56 UTCEPSS rescore
  39. 2026-06-21 01:59 UTCEPSS rescore
  40. 2026-06-21 01:59 UTCEPSS rescore
  41. 2026-06-21 01:30 UTCVendor advisory
  42. 2026-06-20 02:44 UTCVendor advisory
  43. 2026-06-19 19:26 UTCEPSS rescore
  44. 2026-06-19 19:26 UTCEPSS rescore
  45. 2026-06-18 17:52 UTCEPSS rescore
  46. 2026-06-18 17:52 UTCEPSS rescore
  47. 2026-06-17 17:53 UTCEPSS rescore
  48. 2026-06-16 17:53 UTCEPSS rescore
  49. 2026-06-16 09:13 UTCEG score recompute▲ 0.20
  50. 2026-06-16 09:13 UTCVendor advisory
  51. 2026-06-15 17:49 UTCEPSS rescore
  52. 2026-06-15 17:49 UTCEPSS rescore
  53. 2026-06-15 15:28 UTCNVD updateCVSS v3 → 5.3
  54. 2026-06-15 11:23 UTCVendor advisory
  55. 2026-06-14 13:27 UTCVendor advisory
  56. 2026-06-13 23:00 UTCEPSS rescore
  57. 2026-06-12 23:12 UTCEPSS rescore
  58. 2026-06-12 23:12 UTCEPSS rescore
  59. 2026-06-11 19:57 UTCEG score recompute
  60. 2026-06-11 19:56 UTCNVD updatefirst tracked

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 3.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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

Explore the affected products and dependency analysis for 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