Process crash via truncated personal word length
Published Oct 6, 2026 · Updated Oct 6, 2026
Heap corruption in GNU Aspell before 0.60.8.3 allows context-dependent attackers to crash the process with a crafted personal wordlist. WritableDict::add() stores a word's length in one byte while copying the full word into its buffer, so lengths divisible by 256 wrap to zero and corrupt heap state. Exploitation requires a user to load the attacker-supplied wordlist; the documented consequence is a process crash, not code execution.
Summary
What happened
Heap corruption in GNU Aspell before 0.60.8.3 allows context-dependent attackers to crash the process with a crafted personal wordlist. WritableDict::add() stores a word's length in one byte while copying the full word into its buffer, so lengths divisible by 256 wrap to zero and corrupt heap state. Exploitation requires a user to load the attacker-supplied wordlist; the documented consequence is a process crash, not code execution.
The record
- CVE
- CVE-2026-75820
- Published
- Oct 6, 2026
- Updated
- Oct 6, 2026
- Vendor
- CVS Home
- Product
- Aspell
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 6, 2026CVE publishedPublication date reported by the CVE source.
- Oct 6, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <0.60.8.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started