CVE-2026-73076

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 97% 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.0847, runtime/autoload/vimball.vim allows a crafted vimball member named .VimballRecord to overwrite the installation record with attacker-chosen commands. When vimball#RmVimball() later processes the matching record entry, the stored Ex commands, including operating-system commands invoked through :!, execute with the privileges of the user running Vim. This issue is fixed in version 9.2.0847.

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
3%
KEV
Not listed

Published

August 11, 2026

Last Modified

August 11, 2026

Advisory Details (2)

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

commit 581a2f3ac9c6 (vim/vim)

Fix landed in vim/vim commit 581a2f3ac9c6 — awaiting tagged release

https://github.com/vim/vim/commit/581a2f3ac9c6f96a26324f6b2c8c11415fd0d452
github Patch Available

Arbitrary Command Execution via Malicious `.VimballRecord` Entry Replay in `vimball.vim` · Advisory · vim/vim · GitHub

https://github.com/vim/vim/security/advisories/GHSA-r22p-fhw4-84p2

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuvim-tiny (2:7.4.1689-3ubuntu1.5+esm38) @ xenial2026-08-26ubuntu

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.

Weakness Classification(2)

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

All Vendor Advisories

(2)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 22× in last 7d / 42× 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-08-26 07:02 UTCVendor advisory
  2. 2026-08-25 19:44 UTCEG score recompute
  3. 2026-08-25 19:44 UTCVendor advisory
  4. 2026-08-25 13:49 UTCEPSS rescore
  5. 2026-08-25 08:27 UTCVendor advisory
  6. 2026-08-24 20:52 UTCEG score recompute
  7. 2026-08-24 20:52 UTCVendor advisory
  8. 2026-08-24 09:35 UTCEG score recompute
  9. 2026-08-24 09:35 UTCVendor advisory
  10. 2026-08-23 22:18 UTCVendor advisory
  11. 2026-08-23 11:02 UTCEG score recompute
  12. 2026-08-23 11:02 UTCVendor advisory
  13. 2026-08-23 00:19 UTCEPSS rescore
  14. 2026-08-22 23:45 UTCVendor advisory
  15. 2026-08-22 12:28 UTCVendor advisory
  16. 2026-08-22 01:11 UTCEG score recompute
  17. 2026-08-22 01:11 UTCVendor advisory
  18. 2026-08-21 23:49 UTCEPSS rescore
  19. 2026-08-21 02:25 UTCEG score recompute
  20. 2026-08-20 22:56 UTCEPSS rescore
  21. 2026-08-20 03:46 UTCEG score recompute
  22. 2026-08-19 17:04 UTCEPSS rescore
  23. 2026-08-18 17:50 UTCEG score recompute
  24. 2026-08-18 13:49 UTCEPSS rescore
  25. 2026-08-18 13:49 UTCEPSS rescore
Show 17 more
  1. 2026-08-17 19:17 UTCEG score recompute
  2. 2026-08-17 13:47 UTCEPSS rescore
  3. 2026-08-16 20:39 UTCEG score recompute
  4. 2026-08-16 14:56 UTCEPSS rescore
  5. 2026-08-16 14:56 UTCEPSS rescore
  6. 2026-08-16 09:22 UTCEG score recompute
  7. 2026-08-16 02:15 UTCEPSS rescore
  8. 2026-08-15 10:49 UTCEG score recompute
  9. 2026-08-15 01:31 UTCEPSS rescore
  10. 2026-08-14 00:59 UTCEG score recompute
  11. 2026-08-13 22:00 UTCEPSS rescore
  12. 2026-08-12 15:09 UTCEG score recompute
  13. 2026-08-12 13:51 UTCEPSS rescore
  14. 2026-08-11 16:35 UTCEG score recompute
  15. 2026-08-11 16:06 UTCEG score recompute
  16. 2026-08-11 15:41 UTCEG score recompute
  17. 2026-08-11 15:41 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-73076?
CVE-2026-73076 is a high vulnerability published on August 11, 2026. Vim is an open source, command line text editor. Prior to 9.2.0847, runtime/autoload/vimball.vim allows a crafted vimball member named .VimballRecord to overwrite the installation record with attacker-chosen commands. When vimball#RmVimball() later processes the matching record entry, the stored Ex…
When was CVE-2026-73076 disclosed?
CVE-2026-73076 was first published in the National Vulnerability Database on August 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-73076 actively exploited?
CVE-2026-73076 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 97.1% of all scored CVEs.
What is the CVSS score of CVE-2026-73076?
CVE-2026-73076 has a CVSS v3 base score of 8.4 (NVD).
How do I remediate CVE-2026-73076?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-73076, 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

Explore the affected products and dependency analysis for CVE-2026-73076

Explore →

Is Your Infrastructure Affected by CVE-2026-73076?

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