CVE-2026-59857

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.5 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 99% 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 — 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.0725, the single-byte branch of spell_soundfold_sal() in src/spell.c translates a word through a spell file's SAL sound-folding rules into a caller-owned result buffer, but its result writes are guarded with reslen < MAXWLEN, allowing reslen to reach MAXWLEN before res[reslen] = NUL writes one byte past the end of the MAXWLEN-element stack buffer. A boundary-length word passed to soundfold(), or reached via sound-based spell suggestion while a SAL-based spell language is active under a non-multibyte 8-bit encoding, can corrupt the eval_soundfold() stack frame and crash the editor. This issue is fixed in version 9.2.0725.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
25(Track)
EG Risk 25/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%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

July 9, 2026

Last Modified

July 10, 2026

Advisory Details (2)

Auto-updated Jul 9, 2026
Patch available. Sources: github, github_commit.
github Patch Available

Out-of-bounds Write in SAL Soundfolding in Vim < 9.2.0725 · Advisory · vim/vim · GitHub

Affected: 9.2.0698; the single-byte SAL branch

https://github.com/vim/vim/security/advisories/GHSA-m3hf-xcm3-xhm2
github_commit

commit d22ff1c955ff (vim/vim)

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

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

Vendor Advisories for CVE-2026-59857(1)

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:8.1.2269-1ubuntu5.32+esm10) @ focal2026-08-30ubuntu
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 14× in last 7d / 80× 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 119 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-59857?
CVE-2026-59857 is a medium vulnerability published on July 9, 2026. Vim is an open source, command line text editor. Prior to 9.2.0725, the single-byte branch of spellsoundfoldsal() in src/spell.c translates a word through a spell file's SAL sound-folding rules into a caller-owned result buffer, but its result writes are guarded with reslen < MAXWLEN, allowing…
When was CVE-2026-59857 disclosed?
CVE-2026-59857 was first published in the National Vulnerability Database on July 9, 2026, with the most recent update on July 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-59857 actively exploited?
CVE-2026-59857 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 98.6% of all scored CVEs.
What is the CVSS score of CVE-2026-59857?
CVE-2026-59857 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-59857?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-59857, 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-59857

Explore →

Is Your Infrastructure Affected by CVE-2026-59857?

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

Start Free Scan →Browse All CVEs