CVE-2026-55892

MEDIUMPre-NVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 93% 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
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

Vim is an open source, command line text editor. Prior to 9.2.0662, the dump_prefixes() function in src/spell.c walks a spell-file prefix trie iteratively with a depth counter while dumping the prefixes that apply to a word. 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 (prefix[], arridx[], curi[]). A crafted .spl file, loaded when the user dumps the word list, 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.0662.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/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
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
7%
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 Prefix Dump in Vim < 9.2.0662 · Advisory · vim/vim · GitHub

Affected: 9.2.0653) in a sibling trie walker that was

https://github.com/vim/vim/security/advisories/GHSA-qm9w-fmpj-879h
github_commit

commit 8325b193bba5 (vim/vim)

Fix landed in vim/vim commit 8325b193bba5 — awaiting tagged release

https://github.com/vim/vim/commit/8325b193bba5f01e7a7d8241f

Vendor Advisories for CVE-2026-55892(2)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuxxd (2:9.1.2141-1ubuntu4.6) @ resolute2026-08-27ubuntu
redhatvim-main-9.2.780-1.hum12026-07-03redhat

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 11× in last 7d / 71× 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 137 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-55892?
CVE-2026-55892 is a medium vulnerability published on June 25, 2026. Vim is an open source, command line text editor. Prior to 9.2.0662, the dump_prefixes() function in src/spell.c walks a spell-file prefix trie iteratively with a depth counter while dumping the prefixes that apply to a word. The counter is bounded only by the trie structure itself; it is never…
When was CVE-2026-55892 disclosed?
CVE-2026-55892 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-55892 actively exploited?
CVE-2026-55892 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 93.5% of all scored CVEs.
What is the CVSS score of CVE-2026-55892?
CVE-2026-55892 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-55892?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55892, 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-55892

Explore →

Is Your Infrastructure Affected by CVE-2026-55892?

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

Start Free Scan →Browse All CVEs