CVE-2026-75820

LOWPre-NVD 1.81.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This low-severity CVE scores 1.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1% (2nd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 4 sources updated this week
1.8EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 1.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

GNU Aspell contains an integer truncation vulnerability in the WritableDict::add() function in modules/speller/default/writable.cpp. When loading a personal wordlist, the word length is stored as a single byte, causing truncation for words whose length is a multiple of 256. This leads to heap corruption. An attacker can exploit this by convincing a user to run aspell with a crafted personal wordlist containing such a word, resulting in denial of service.

This issue was fixed in commit 782ce94e4dc71eaec4ee1bd945eb3b9c47c5387d which will be released in version 0.60.8.3.

CVSS v3
1.8
EG Score
1.8LOWmedium confidence
EG Risk
8
EG Risk 8/100

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 (value × EchelonGraph’s weight)
Severity18% × 45%
The EG Score, 1.8 of 10.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
2nd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 6, 2026

Last Modified

October 6, 2026

Vendor Advisories for CVE-2026-75820(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
aspell0.60.8-4 ... 0.60.8.2-3 (12 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
aspell0.60.8.1-4 ... 0.60.8.2-3 (6 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
aspell0.60.8.1-4 ... 0.60.8.2-3 (6 versions)
  • every version on: no fix on record
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 21× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  2. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  3. 2026-10-12 15:39 UTCEG score recompute
  4. 2026-10-11 19:24 UTCEG score recompute
  5. 2026-10-11 16:40 UTCEG score recompute
  6. 2026-10-11 13:59 UTCEG score recompute
  7. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  8. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  9. 2026-10-09 17:14 UTCEG score recompute
  10. 2026-10-09 17:14 UTCVendor advisory
  11. 2026-10-09 17:14 UTCGHSA enrichmentGHSA-7gjr-5wh9-g7w9 · GitHub severity LOW
  12. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  13. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  14. 2026-10-06 15:16 UTCGHSA enrichmentGHSA-7gjr-5wh9-g7w9 · GitHub severity LOW
  15. 2026-10-06 13:29 UTCEG score recompute
  16. 2026-10-06 13:29 UTCGHSA enrichmentGHSA-7gjr-5wh9-g7w9 · GitHub severity LOW
  17. 2026-10-06 12:55 UTCEG score recompute
  18. 2026-10-06 12:55 UTCGHSA enrichmentGHSA-7gjr-5wh9-g7w9 · GitHub severity LOW
  19. 2026-10-06 11:27 UTCEG score recompute
  20. 2026-10-06 11:00 UTCEG score recomputeFirst assessed: 1.8 LOW
  21. 2026-10-06 10:59 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-75820?
CVE-2026-75820 is a low-severity vulnerability; its CVE record was published on October 6, 2026. GNU Aspell contains an integer truncation vulnerability in the WritableDict::add() function in modules/speller/default/writable.cpp. When loading a personal wordlist, the word length is stored as a single byte, causing truncation for words whose length is a multiple of 256. This leads to heap…
When was the CVE record for CVE-2026-75820 published?
The CVE record for CVE-2026-75820 was published on October 6, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 6, 2026; the record at its source may have been updated since.
Is CVE-2026-75820 actively exploited?
CVE-2026-75820 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-75820?
CVE-2026-75820 has a CVSS base score of 1.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-75820?
A fix for CVE-2026-75820 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-75820 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-75820

Explore →

Is Your Infrastructure Affected by CVE-2026-75820?

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