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%, 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
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%CVSS: 7.1Exploit: None knownExposed: 0

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.1(medium)
EG Risk
37(Track)
EG Risk 37/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
Severity71% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
4%
KEV
Not listed

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
github Patch Available

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(1)

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
ubuntuxxd (2:9.1.2141-1ubuntu4.9) @ resolute2026-09-19ubuntu
ubuntuxxd (2:9.1.0016-1ubuntu7.20) @ noble2026-09-19ubuntu
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 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(2)

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

Additional Vendor Advisories

(3)

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

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 in the National Vulnerability Database 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% probability of exploitation in the next 30 days, which ranks it in the top 95.7% of all scored CVEs.
What is the CVSS score of CVE-2026-73073?
CVE-2026-73073 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-73073?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-73073, 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-73073

Explore →

Is Your Infrastructure Affected by CVE-2026-73073?

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

Start Free Scan →Browse All CVEs