CVE-2026-47162

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 82% 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
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

A fix is available — apply it.

Vim is an open source, command line text editor. Prior to version 9.2.0495, a Vimscript code injection vulnerability exists in s:NetrwBookHistSave() in the netrw plugin (runtime/pack/dist/opt/netrw/autoload/netrw.vim) when serializing browsed directory paths to the history file ~/.vim/.netrwhist. A directory name derived from the filesystem is interpolated into a single-quoted Vimscript string literal without escaping embedded single quotes, allowing a crafted directory name to break out of the string context and execute arbitrary Vimscript, including shell commands via system() and :!, the next time the history file is sourced. This issue has been patched in version 9.2.0495.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity88% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
18%
KEV
Not listed

Published

June 11, 2026

Last Modified

September 18, 2026

Advisory Details (2)

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

Vimscript Code Injection in netrw NetrwBookHistSave() via crafted directory name affects Vim < 9.2.0495 · Advisory · vim/vim · GitHub

https://github.com/vim/vim/security/advisories/GHSA-crm5-rh6j-2c7c
github_commit

commit f08ab2f4d7d2 (vim/vim)

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

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

Patch Availability(9)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuxxd (2:9.1.2141-1ubuntu4.5) @ resolute2026-09-18ubuntu
redhatvim-2:7.4.629-8.el7_9.22026-09-17redhat
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 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(3)

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 12× in last 7d / 55× 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 257 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-47162?
CVE-2026-47162 is a high vulnerability published on June 11, 2026. Vim is an open source, command line text editor. Prior to version 9.2.0495, a Vimscript code injection vulnerability exists in s:NetrwBookHistSave() in the netrw plugin (runtime/pack/dist/opt/netrw/autoload/netrw.vim) when serializing browsed directory paths to the history file ~/.vim/.netrwhist. A…
When was CVE-2026-47162 disclosed?
CVE-2026-47162 was first published in the National Vulnerability Database on June 11, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47162 actively exploited?
CVE-2026-47162 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 81.9% of all scored CVEs.
What is the CVSS score of CVE-2026-47162?
CVE-2026-47162 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-47162?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47162, 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-47162

Explore →

Is Your Infrastructure Affected by CVE-2026-47162?

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