CVE-2026-73077

HIGHPre-NVD 8.48.4—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 96% 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, secondary
Trending — 3 sources updated this week
8.4EG
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.4Exploit: None knownExposed: 0

A fix is available — apply it.

Vim is an open source, command line text editor. Prior to 9.2.0839, the runtime/ftplugin/sh.vim, runtime/ftplugin/zsh.vim, and runtime/ftplugin/ps1.vim filetype plugins pass attacker-controlled Visual-mode selections from K through keywordprg commands without safely separating shell arguments. fnameescape() and PATH_ESC_CHARS do not neutralize shell metacharacters before ShKeywordPrg, ZshKeywordPrg, or GetHelp invokes bash, zsh, or PowerShell, allowing arbitrary operating-system commands to execute with the privileges of the user running Vim. This issue is fixed in version 9.2.0839.

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

Published

August 11, 2026

Last Modified

September 9, 2026

Advisory Details (2)

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

commit c5a82fe013e7 (vim/vim)

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

https://github.com/vim/vim/commit/c5a82fe013e73c98004ad7cd4f906b1ad1ed610e
github Patch Available

Arbitrary Code Execution via Shell Keyword Lookup in Vim < 9.2.0839 · Advisory · vim/vim · GitHub

https://github.com/vim/vim/security/advisories/GHSA-r5v6-q6j8-8qw2

Vendor Advisories for CVE-2026-73077(2)

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

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuvim-tiny (2:7.4.1689-3ubuntu1.5+esm38) @ xenial2026-09-19ubuntu
redhatvim-2:9.1.083-9.el10_2.202026-09-10redhat
redhatvim-2:8.2.2637-26.el9_8.212026-09-10redhat

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)
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
vim—9.2.0854-r0—
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.0782-1 (18 versions)2:9.2.0858-1—

Weakness Classification(1)

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

Additional Vendor Advisories

(2)

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 25× in last 7d / 104× 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 127 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-73077?
CVE-2026-73077 is a high vulnerability published on August 11, 2026. Vim is an open source, command line text editor. Prior to 9.2.0839, the runtime/ftplugin/sh.vim, runtime/ftplugin/zsh.vim, and runtime/ftplugin/ps1.vim filetype plugins pass attacker-controlled Visual-mode selections from K through keywordprg commands without safely separating shell arguments.…
When was CVE-2026-73077 disclosed?
CVE-2026-73077 was first published in the National Vulnerability Database on August 11, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-73077 actively exploited?
CVE-2026-73077 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.2% of all scored CVEs.
What is the CVSS score of CVE-2026-73077?
CVE-2026-73077 has a CVSS v3 base score of 8.4 (NVD).
How do I remediate CVE-2026-73077?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-73077, 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-73077

Explore →

Is Your Infrastructure Affected by CVE-2026-73077?

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

Start Free Scan →Browse All CVEs