CVE-2026-73076

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.8 under NVD CVSS v3. EPSS exploit probability: 0.1% (2nd 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, nvd
Trending — Patch released this week
7.8EG
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.8Exploit: None knownExposed services: Not assessed

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
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/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
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
2nd
KEV
Not listed

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

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). 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 11, 2026

Last Modified

October 6, 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
githubMentions a patch (unverified)

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

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhai/base-image-cpu-rhel9:17907036562026-10-05redhat
redhatrhai/base-image-cuda-13.0-rhel9:17907036452026-10-05redhat
redhatrhai/base-image-cuda-12.9-rhel9:17907037062026-10-05redhat
redhatrhai/base-image-rocm-7.14-rhel9:17907035542026-10-05redhat
redhatrhai/base-image-neuron-rhel9:17907035572026-10-05redhat
redhatrhai/base-image-spyre-rhel9:17907036302026-10-05redhat
redhatrhai/base-image-rubin-rhel9:17907037072026-10-05redhat
redhatrhai/base-image-tpu-rhel9:17907035542026-10-05redhat
redhatrhai/base-image-cuda-12.9-rhel9:17907036302026-10-01redhat
redhatrhai/base-image-spyre-rhel9:17907035972026-10-01redhat
redhatrhai/base-image-gaudi-rhel9:17907035532026-10-01redhat
redhatrhai/base-image-cuda-13.0-rhel9:17907036412026-10-01redhat
redhatrhai/base-image-rocm-7.1-rhel9:17907035412026-10-01redhat
redhatrhai/base-image-gaudi-rhel9:17907035522026-10-01redhat
redhatrhai/base-image-rocm-6.4-rhel9:17907035452026-10-01redhat
redhatrhai/base-image-neuron-rhel9:17907035422026-10-01redhat
redhatrhai/base-image-tpu-rhel9:17907035392026-10-01redhat
redhatrhai/base-image-cpu-rhel9:17907036312026-10-01redhat
redhatrhai/base-image-cpu-rhel9:17907035902026-10-01redhat
redhatrhai/base-image-spyre-rhel9:17907035682026-10-01redhat
redhatrhai/base-image-rocm-rhel9:17907034942026-10-01redhat
redhatrhai/base-image-spyre-rhel9:17907035792026-10-01redhat
redhatrhai/base-image-rocm-6.4-rhel9:17907035242026-10-01redhat
redhatrhai/base-image-cuda-13.0-rhel9:17907036012026-10-01redhat
redhatrhai/base-image-neuron-rhel9:17907035162026-10-01redhat
redhatrhai/base-image-rocm-rhel9:17907035062026-10-01redhat
redhatrhai/base-image-cpu-rhel9:17907036152026-10-01redhat
redhatrhai/base-image-tpu-rhel9:17907034972026-10-01redhat
redhatrhai/base-image-cuda-rhel9:17907035862026-10-01redhat
redhatrhai/base-image-cuda-12.9-rhel9:17907036082026-10-01redhat

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.

All Vendor Advisories

(25)

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 18× in last 7d / 87× 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 178 total refreshes for this CVE.

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

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 on August 11, 2026, with the most recent update on October 6, 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.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-73076?
CVE-2026-73076 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-73076?
A fix for CVE-2026-73076 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-73076 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-73076

Explore →

Is Your Infrastructure Affected by CVE-2026-73076?

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