CVE-2026-73073

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1% (3rd percentile of EPSS-scored CVEs). 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 — Patch released this week
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 7.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Vim is an open source, command line text editor. Prior to 9.2.0845, StructMembers() in runtime/autoload/ccomplete.vim constructs and executes a vimgrep command using an insufficiently escaped typeref: or typename: value from a tags file, allowing an unterminated collection followed by a command separator to execute arbitrary Ex and operating-system commands when a user invokes C omni-completion with CTRL-X CTRL-O on a member access whose type is resolved from that tags file. This issue is fixed in version 9.2.0845.

CVSS v3
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
37
EG Risk 37/100CISA SSVC

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
Severity71% × 45%
Exploitation0% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.1%
EPSS %ILE
3rd
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 18, 2026

Last Modified

September 18, 2026

Advisory Details (2)

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

commit 2f628d810495 (vim/vim)

Fix landed in vim/vim commit 2f628d810495 — awaiting tagged release

https://github.com/vim/vim/commit/2f628d8104958fa7421664f792ca6d4f7a39a10f
githubMentions a patch (unverified)

Arbitrary Ex Command Execution in C Omni-Completion in Vim < 9.2.0845 · Advisory · vim/vim · GitHub

https://github.com/vim/vim/security/advisories/GHSA-cx73-phcg-3j5g

Vendor Advisories for CVE-2026-73073(5)

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

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntuvim-tiny (2:7.4.1689-3ubuntu1.5+esm39) @ xenial2026-10-07ubuntu
ubuntuxxd (2:9.1.2141-1ubuntu4.9) @ resolute2026-10-07ubuntu
redhatvim-2:8.2.2637-26.el9_8.232026-10-06redhat
redhatvim-2:9.1.083-9.el10_2.222026-10-05redhat
redhatvim-main-9.2.967-1.1.hum12026-08-20redhat

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 rangeFix by version rangeDependents
vim—
  • every version up to 9.2.0854-r0: fixed in 9.2.0854-r0
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
vim2:9.0.1378-2 ... 2:9.2.0858-1 (45 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
vim2:9.1.1230-2 ... 2:9.2.0858-1 (19 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
vim2:9.1.1230-2 ... 2:9.2.0782-1 (18 versions)
  • every version up to 2:9.2.0858-1: fixed in 2:9.2.0858-1
—

Weakness Classification(2)

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 16× in last 7d / 92× 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 154 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-73073?
CVE-2026-73073 is a high vulnerability published on August 18, 2026. Vim is an open source, command line text editor. Prior to 9.2.0845, StructMembers() in runtime/autoload/ccomplete.vim constructs and executes a vimgrep command using an insufficiently escaped typeref: or typename: value from a tags file, allowing an unterminated collection followed by a command…
When was CVE-2026-73073 disclosed?
CVE-2026-73073 was first published on August 18, 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-73073 actively exploited?
CVE-2026-73073 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (3rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-73073?
CVE-2026-73073 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-73073?
A fix for CVE-2026-73073 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-73073 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-73073

Explore →

Is Your Infrastructure Affected by CVE-2026-73073?

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

Book a Demo →Browse All CVEs