Quick answers
- Is CVE-2026-59857 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-59857 being exploited in the wild.
- How severe is CVE-2026-59857?
- Informational severity, with a CVSS score of 5.6, published 9 July 2026.
- Which products and versions are affected?
- Vim < 9.2.0725.
- Is there a fix for CVE-2026-59857?
- A patch was published on 2026-07-09: Fix included in Vim patch 9.2.0725 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-59857 attacked?
- It is attacked with local access, in a network appliance.
- Am I affected by CVE-2026-59857?
- Check whether you run Vim at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An off-by-one stack-based out-of-bounds write exists in the `spell_soundfold_sal()` function within `src/spell.c`. The vulnerability occurs in the single-byte branch (used for 8-bit encodings like latin1) where result writes are guarded by `reslen < MAXWLEN`. This allows `reslen` to reach the value of `MAXWLEN`, causing the subsequent NUL-terminator assignment `res[reslen] = NUL` to write one byte past the end of the `MAXWLEN`-sized stack buffer. An attacker can trigger this by passing a boundary-length word to the `soundfold()` function or through sound-based spell suggestions when a SAL-based spell language is active. This results in stack frame corruption and a process crash. The issue is fixed in version 9.2.0725.
Affected products
- Vim Vim < 9.2.0725
Timeline
- 2026-06-24: advisory: GitHub Security Advisory published
- 2026-07-09: disclosed: CVE published to NVD
- 2026-07-09: patched: Fix included in Vim patch 9.2.0725