CVE-2026-73072

HIGHNVD 7.37.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 7.3 under NVD CVSS v3. EPSS exploit probability: 0.1% (1st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — Patch released this week
7.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 7.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Vim is an open source, command line text editor. Prior to 9.2.0846, set_sofo() in src/spellfile.c reuses sl_sal_first[] without resetting values left by set_sal_first(), so a crafted spell file containing an SN_SAL section before an SN_SOFO section causes under-counted mapping lists and attacker-influenced writes beyond a heap allocation. This issue is fixed in version 9.2.0846.

CVSS v3
7.3
EG Score
7.3HIGHmedium confidence
EG Risk
33
EG Risk 33/100

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 (value × EchelonGraph’s weight)
Severity73% × 45%
The EG Score, 7.3 of 10.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
1st
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track 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). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

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 05c41c922309 (vim/vim)

Fix landed in vim/vim commit 05c41c922309 — awaiting tagged release

https://github.com/vim/vim/commit/05c41c922309c7a11b6ec2f124be66551c90d66a
GitHub advisoryMentions a patch (unverified)

Heap Buffer Overflow when Loading a Spell File in Vim < 9.2.0846 · Advisory · vim/vim · GitHub

https://github.com/vim/vim/security/advisories/GHSA-9jqx-hgpr-6v64

Vendor Advisories for CVE-2026-73072(20)

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

Patch Availability(30)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhai/base-image-cuda-12.9-rhel9:17912322572026-10-12redhat
redhatrhai/base-image-cuda-13.0-rhel9:17912318202026-10-12redhat
redhatrhai/base-image-rocm-7.14-rhel9:17907035542026-10-05redhat
redhatrhai/base-image-rubin-rhel9:17907037072026-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-spyre-rhel9:17907036302026-10-05redhat
redhatrhai/base-image-tpu-rhel9:17907035542026-10-05redhat
redhatrhai/base-image-neuron-rhel9:17907035572026-10-05redhat
redhatrhai/base-image-cpu-rhel9:17907036562026-10-05redhat
redhatrhai/base-image-gaudi-rhel9:17907035532026-10-01redhat
redhatrhai/base-image-tpu-rhel9:17907035392026-10-01redhat
redhatrhai/base-image-neuron-rhel9:17907035422026-10-01redhat
redhatrhai/base-image-cpu-rhel9:17907036312026-10-01redhat
redhatrhai/base-image-rocm-7.1-rhel9:17907035412026-10-01redhat
redhatrhai/base-image-gaudi-rhel9:17907035522026-10-01redhat
redhatrhai/base-image-cuda-12.9-rhel9:17907036302026-10-01redhat
redhatrhai/base-image-cuda-13.0-rhel9:17907036412026-10-01redhat
redhatrhai/base-image-spyre-rhel9:17907035972026-10-01redhat
redhatrhai/base-image-rocm-6.4-rhel9:17907035452026-10-01redhat
redhatrhai/base-image-cpu-rhel9:17907035902026-10-01redhat
redhatrhai/base-image-rocm-6.4-rhel9:17907035242026-10-01redhat
redhatrhai/base-image-rocm-rhel9:17907034942026-10-01redhat
redhatrhai/base-image-spyre-rhel9:17907035792026-10-01redhat
redhatrhai/base-image-cuda-12.9-rhel9:17907036082026-10-01redhat
redhatrhai/base-image-rocm-rhel9:17907035062026-10-01redhat
redhatrhai/base-image-cuda-13.0-rhel9:17907036012026-10-01redhat
redhatrhai/base-image-rocm-7.0-rhel9:17907035162026-10-01redhat
redhatrhai/base-image-neuron-rhel9:17907035162026-10-01redhat
redhatrhai/base-image-spyre-rhel9:17907035682026-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 13× in last 7d / 86× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 191 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 91 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

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

Frequently asked(5)

What is CVE-2026-73072?
CVE-2026-73072 is a high-severity vulnerability; its CVE record was published on August 11, 2026. Vim is an open source, command line text editor. Prior to 9.2.0846, setsofo() in src/spellfile.c reuses slsalfirst[] without resetting values left by setsalfirst(), so a crafted spell file containing an SNSAL section before an SN_SOFO section causes under-counted mapping lists and…
When was the CVE record for CVE-2026-73072 published?
The CVE record for CVE-2026-73072 was published on August 11, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 6, 2026; the record at its source may have been updated since.
Is CVE-2026-73072 actively exploited?
CVE-2026-73072 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-73072?
CVE-2026-73072 has a CVSS v3 base score of 7.3 (NVD).
How do I remediate CVE-2026-73072?
A fix for CVE-2026-73072 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-73072 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-73072

Explore →

Is Your Infrastructure Affected by CVE-2026-73072?

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

Book a Demo →Browse All CVEs