CVE-2026-73072

HIGHPre-NVD 8.58.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.5 under the CNA's CVSS (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: cna:github_m, epss
Trending — Patch released this week
8.5EG
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.5Exploit: None knownExposed: 0

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
8.5
EG Score
8.5(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
Severity85% × 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

September 17, 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 Patch Available

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

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 / EcosystemFixed in / PatchReleasedSource
ubuntuxxd (2:8.1.2269-1ubuntu5.32+esm12) @ focal2026-09-18ubuntu
redhatvim-2:7.4.629-8.el7_9.22026-09-17redhat
redhatvim-2:9.1.083-9.el10_2.202026-09-10redhat
redhatvim-2:8.0.1763-31.el8_10.72026-09-10redhat
redhatvim-2:8.2.2637-26.el9_8.212026-09-10redhat

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

(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 22× in last 7d / 98× 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 121 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-73072?
CVE-2026-73072 is a high vulnerability 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 CVE-2026-73072 disclosed?
CVE-2026-73072 was first published in the National Vulnerability Database on August 11, 2026, with the most recent update on September 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-73072 actively exploited?
CVE-2026-73072 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.4% of all scored CVEs.
What is the CVSS score of CVE-2026-73072?
CVE-2026-73072 has a CVSS v4.0 base score of 8.5 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-73072?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-73072, 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-73072

Explore →

Is Your Infrastructure Affected by CVE-2026-73072?

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

Start Free Scan →Browse All CVEs