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.
CVE-2026-59857
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).
- Lower severity and no public exploit yet
A fix is available — apply it.
- 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 computedSeverity55% × 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, 2026Out-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-xhm2commit d22ff1c955ff (vim/vim)
Fix landed in vim/vim commit d22ff1c955ff — awaiting tagged release
https://github.com/vim/vim/commit/d22ff1c955ff87e8273210eae125aab0e85b6c30Vendor Advisories for CVE-2026-59857(4)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2026:66366Red Hat Product SecurityHigh
Red Hat Security Advisory: vim security update
- RHSA-2026:66348Red Hat Product SecurityHigh
Red Hat Security Advisory: vim security update
- RHSA-2026:66336Red Hat Product SecurityHigh
Red Hat Security Advisory: vim security update
- RHSA-2026:35387Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
Patch Availability(5)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | xxd (2:8.2.3995-1ubuntu2.34) @ jammy | 2026-09-18 | ubuntu |
| redhat | vim-2:9.1.083-9.el10_2.20 | 2026-09-10 | redhat |
| redhat | vim-2:8.0.1763-31.el8_10.7 | 2026-09-10 | redhat |
| redhat | vim-2:8.2.2637-26.el9_8.21 | 2026-09-10 | redhat |
| redhat | vim-main-9.2.780-1.hum1 | 2026-07-03 | redhat |
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
(5 across 5 ecosystems)
Alpine:v3.23(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| vim | — | 9.2.0854-r0 | — |
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| vim | 2:8.2.2434-3 ... 2:9.2.0858-1 (63 versions) | — | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| vim | 2:9.0.1378-2 ... 2:9.2.0858-1 (45 versions) | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| vim | 2:9.1.1230-2 ... 2:9.2.0858-1 (19 versions) | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| vim | 2: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 10× in last 7d / 47× 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 143 total refreshes for this CVE.
- 2026-09-18 05:26 UTCEG score recompute
- 2026-09-18 05:26 UTCVendor advisory
- 2026-09-17 19:31 UTCEPSS rescore
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-15 03:11 UTCEPSS rescore
- 2026-09-14 07:51 UTCEG score recompute
- 2026-09-14 07:51 UTCVendor advisory
- 2026-09-13 16:47 UTCEPSS rescore
- 2026-09-13 08:16 UTCEG score recompute
- 2026-09-13 08:16 UTCVendor advisory
- 2026-09-12 03:19 UTCEG score recompute
- 2026-09-12 03:19 UTCVendor advisory
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-10 09:35 UTCEPSS rescore
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-08 03:21 UTCEG score recompute
- 2026-09-08 03:21 UTCVendor advisory
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-05 21:59 UTCEG score recompute
- 2026-09-05 21:59 UTCVendor advisory
- 2026-09-04 05:07 UTCEPSS rescore
- 2026-09-01 13:54 UTCEPSS rescore
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 06:42 UTCEG score recompute
Show 75 moreShow fewer
- 2026-08-30 06:42 UTCVendor advisory
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-27 21:43 UTCEG score recompute
- 2026-08-27 21:43 UTCVendor advisory
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-26 03:46 UTCEG score recompute
- 2026-08-26 03:46 UTCVendor advisory
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 03:31 UTCEG score recompute
- 2026-08-25 03:31 UTCVendor advisory
- 2026-08-24 03:57 UTCVendor advisory
- 2026-08-23 03:14 UTCEG score recompute
- 2026-08-23 03:14 UTCVendor advisory
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 03:35 UTCEG score recompute
- 2026-08-22 03:35 UTCVendor advisory
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 03:46 UTCEG score recompute
- 2026-08-21 03:46 UTCVendor advisory
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 03:38 UTCEG score recompute
- 2026-08-20 03:38 UTCVendor advisory
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 03:59 UTCVendor advisory
- 2026-08-18 04:24 UTCEG score recompute
- 2026-08-18 04:24 UTCVendor advisory
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 04:47 UTCEG score recompute
- 2026-08-17 04:47 UTCVendor advisory
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 05:13 UTCEG score recompute
- 2026-08-16 05:13 UTCVendor advisory
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 05:40 UTCEG score recompute
- 2026-08-15 05:40 UTCVendor advisory
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 06:06 UTCEG score recompute
- 2026-08-14 06:06 UTCVendor advisory
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 06:33 UTCEG score recompute
- 2026-08-13 06:33 UTCVendor advisory
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-12 06:59 UTCEG score recompute
- 2026-08-12 06:59 UTCVendor advisory
- 2026-08-11 07:25 UTCEG score recompute
- 2026-08-11 07:25 UTCVendor advisory
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 07:51 UTCEG score recompute
- 2026-08-10 07:51 UTCVendor advisory
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 08:18 UTCEG score recompute
- 2026-08-09 08:18 UTCVendor advisory
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 08:45 UTCEG score recompute
- 2026-08-08 08:45 UTCVendor advisory
- 2026-08-07 09:11 UTCEG score recompute
- 2026-08-07 09:11 UTCVendor advisory
- 2026-08-06 13:47 UTCEPSS rescore
- 2026-08-06 09:38 UTCEG score recompute
- 2026-08-06 09:38 UTCVendor advisory
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 10:05 UTCEG score recompute
- 2026-08-05 10:05 UTCVendor advisory
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 10:39 UTCEPSS rescore
- 2026-08-04 10:11 UTCEG score recompute
- 2026-08-04 10:11 UTCVendor advisory
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-03 09:50 UTCVendor advisory
- 2026-08-02 10:14 UTCEG score recompute
- 2026-08-02 10:14 UTCVendor advisory
- 2026-08-02 02:27 UTCEPSS rescore
- 2026-08-01 10:39 UTCEG score recompute
Frequently asked(5)
What is CVE-2026-59857?
When was CVE-2026-59857 disclosed?
Is CVE-2026-59857 actively exploited?
What is the CVSS score of CVE-2026-59857?
How do I remediate CVE-2026-59857?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-59857
Is Your Infrastructure Affected by CVE-2026-59857?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.