Quick answers
- Is CVE-2026-75819 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-75819 being exploited in the wild.
- How severe is CVE-2026-75819?
- Informational severity, published 6 October 2026.
- Which products and versions are affected?
- Gnu Aspell before 0.60.8.3.
- Is there a fix for CVE-2026-75819?
- Yes: fixed in 0.60.8.3. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-75819 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-75819?
- Check whether you run Gnu Aspell 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.
How to fix
- Fixed in: 0.60.8.3
Technical details
The ReadOnlyDict::load() function in readonly_ws.cpp fails to validate offset fields from .rws dictionary file headers before using them as indices into a heap buffer, resulting in out-of-bounds read (CWE-125). An attacker can craft a malicious dictionary file and trigger the vulnerability when a user runs aspell with the file supplied via --master, --dict-dir, or configuration options. Exploitation enables heap memory disclosure or denial of service via application crash; a fix is available in version 0.60.8.3.
Affected products
- GNU Aspell before 0.60.8.3
Timeline
- 2026-10-06: disclosed
- 2026-10-06: patched: Fix available in commit 941953b25031bc9104e83f58e138a664b8dedc3f, released in version 0.60.8.3