CVE-2026-55693

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.8 under NVD CVSS v3. 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, 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%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

Vim is an open source, command line text editor. Prior to 9.2.0653, the tree_count_words() function in src/spellfile.c fills in the word-count fields of a spell-file word trie by walking it iteratively with a depth counter. The counter is bounded only by the trie structure itself; it is never checked against the size of the fixed MAXWLEN-element stack arrays it indexes (arridx[], curi[], wordcount[]). A crafted .spl/.sug file pair, loaded when the user invokes spell suggestion, can drive the descent arbitrarily deep, so the function writes past the end of those arrays. This is a stack out-of-bounds write that corrupts the call frame and crashes the editor. This vulnerability is fixed in 9.2.0653.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

June 25, 2026

Last Modified

June 26, 2026

Advisory Details (2)

Auto-updated Jun 25, 2026
Patch available. Sources: github_commit, github.
github Patch Available

Out-of-bounds Write in Spell File Word Count in Vim < 9.2.0653 · Advisory · vim/vim · GitHub

https://github.com/vim/vim/security/advisories/GHSA-wgh4-64f7-q3jq
github_commit

commit a80874d9b84a (vim/vim)

Fix landed in vim/vim commit a80874d9b84a — awaiting tagged release

https://github.com/vim/vim/commit/a80874d9b84a01040e3d1aef2d4a59e1934dafb7

Vendor Advisories for CVE-2026-55693(9)

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

Patch Availability(9)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuxxd (2:9.1.2141-1ubuntu4.6) @ resolute2026-08-21ubuntu
redhatrhcos-4.22.9.8.202608130832-02026-08-18redhat
redhatvim-2:9.1.083-5.el10_0.42026-08-17redhat
redhatrhui5/rhua-rhel9:17865335292026-08-12redhat
redhatinsights-proxy/insights-proxy-container-rhel9:17864336562026-08-11redhat
redhatvim-2:9.1.083-9.el10_2.122026-07-31redhat
redhatvim-2:8.0.1763-31.el8_102026-07-31redhat
redhatvim-2:8.2.2637-26.el9_8.132026-07-29redhat
redhatvim-main-9.2.725-1.hum12026-06-26redhat

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)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
vim2:8.2.2434-3 ... 2:9.2.0858-1 (63 versions)——
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.0524-1 (17 versions)2:9.2.0782-1—

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

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 26× in last 7d / 94× 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 164 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-55693?
CVE-2026-55693 is a high vulnerability published on June 25, 2026. Vim is an open source, command line text editor. Prior to 9.2.0653, the treecountwords() function in src/spellfile.c fills in the word-count fields of a spell-file word trie by walking it iteratively with a depth counter. The counter is bounded only by the trie structure itself; it is never checked…
When was CVE-2026-55693 disclosed?
CVE-2026-55693 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55693 actively exploited?
CVE-2026-55693 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-55693?
CVE-2026-55693 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-55693?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55693, 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-55693

Explore →

Is Your Infrastructure Affected by CVE-2026-55693?

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

Start Free Scan →Browse All CVEs