CVE-2026-28417

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

A fix is available — apply it.

Vim is an open source, command line text editor. Prior to version 9.2.0073, an OS command injection vulnerability exists in the netrw standard plugin bundled with Vim. By inducing a user to open a crafted URL (e.g., using the scp:// protocol handler), an attacker can execute arbitrary shell commands with the privileges of the Vim process. Version 9.2.0073 fixes the issue.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
36(Track)
EG Risk 36/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
Severity78% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
65%
KEV
Not listed

Published

February 27, 2026

Last Modified

June 17, 2026

Advisory Details (3)

Auto-updated Aug 2, 2026
Patch available. Sources: github_commit, github.
generic

oss-security - [vim-security] OS Command Injection in netrw affects Vim < 9.2.0073

http://www.openwall.com/lists/oss-security/2026/02/27/6
github Patch Available

OS Command Injection in netrw affects Vim < 9.2.0073 · Advisory · vim/vim · GitHub

https://github.com/vim/vim/security/advisories/GHSA-m3xh-9434-g336
github_commit

commit 79348dbbc093 (vim/vim)

Fix landed in vim/vim commit 79348dbbc093 — awaiting tagged release

https://github.com/vim/vim/commit/79348dbbc09332130f4c860

Patch Availability(30)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuxxd (2:8.2.3995-1ubuntu2.26) @ jammy2026-06-12ubuntu
redhatrhaiis/model-opt-cuda-rhel9:17806819842026-06-10redhat
redhatrhcos-417.94.202605112123-02026-05-20redhat
redhatrhcos-415.92.202605060220-02026-05-13redhat
redhatrhcos-414.92.202605060243-02026-05-13redhat
redhatrhaiis/vllm-spyre-rhel9:17782445462026-05-12redhat
redhatrhaiis/model-opt-cuda-rhel9:17782445592026-05-11redhat
redhatrhaiis/vllm-rocm-rhel9:17782445312026-05-11redhat
redhatrhcos-412.86.202604281506-02026-05-08redhat
redhatrhcos-416.94.202604211449-02026-04-30redhat
redhatrhui5/rhua-tp-rhel9:17774595042026-04-29redhat
redhatrhui5/rhua-rhel9:17768688422026-04-23redhat
redhatinsights-proxy/insights-proxy-container-rhel9:17768689612026-04-22redhat
redhatrhcos-418.94.202604140044-02026-04-22redhat
redhatrhcos-413.92.202604080111-02026-04-16redhat
redhatrhcos-4.19.9.6.202604080618-02026-04-16redhat
redhatvim-2:8.2.2637-23.el9_7.22026-04-15redhat
redhatvim-2:9.1.083-6.el10_1.32026-04-13redhat
redhatrhaiis/vllm-cuda-rhel9:17757405632026-04-09redhat
redhatvim-2:8.0.1763-20.el8_8.12026-04-07redhat
redhatvim-2:8.0.1763-19.el8_6.52026-04-07redhat
redhatvim-2:8.0.1763-15.el8_4.12026-04-07redhat
redhatvim-2:8.0.1763-22.el8_10.12026-04-07redhat
redhatvim-2:8.0.1763-13.el8_2.12026-04-07redhat
redhatvim-2:8.2.2637-16.el9_0.42026-04-06redhat
redhatvim-2:8.2.2637-20.el9_2.12026-04-06redhat
redhatvim-2:7.4.629-8.el7_9.12026-04-06redhat
redhatvim-2:8.2.2637-22.el9_6.22026-04-02redhat
redhatvim-2:9.1.083-5.el10_0.22026-04-02redhat
redhatvim-2:8.2.2637-20.el9_4.22026-04-02redhat

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

(5 across 5 ecosystems)
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
vim9.2.0078-r0
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.1.2141-1 (8 versions)2:9.2.0119-1

Weakness Classification(2)

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

Additional Vendor Advisories

(9)

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-28417?
CVE-2026-28417 is a high vulnerability published on February 27, 2026. Vim is an open source, command line text editor. Prior to version 9.2.0073, an OS command injection vulnerability exists in the netrw standard plugin bundled with Vim. By inducing a user to open a crafted URL (e.g., using the scp:// protocol handler), an attacker can execute arbitrary shell…
When was CVE-2026-28417 disclosed?
CVE-2026-28417 was first published in the National Vulnerability Database on February 27, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-28417 actively exploited?
CVE-2026-28417 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 35.0% of all scored CVEs.
What is the CVSS score of CVE-2026-28417?
CVE-2026-28417 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-28417?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-28417, 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-28417

Explore →

Is Your Infrastructure Affected by CVE-2026-28417?

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