CVE-2026-103658 GNU CVE debrief

Who should care

Defenders responsible for GNU Aspell deployments should assess exposure and prioritize verification and updates. They should also restrict loading untrusted dictionaries and monitor for suspicious dictionary loading activity. Defenders should review compensating controls for exposed systems while remediation is scheduled and verified.

Why it matters

CVE-2026-103658 is a heap-based buffer overflow write vulnerability in GNU Aspell 0.60.8.2. Defenders should prioritize verifying GNU Aspell versions and updating to 0.60.8.3 or later. They should also restrict loading untrusted dictionaries.

• Denial of service due to heap memory corruption
• Potential code execution due to heap memory corruption
• Verification of GNU Aspell versions and updates required
• Restricting loading of untrusted dictionaries recommended

Technical summary

GNU Aspell 0.60.8.2 contains a heap-based buffer overflow write in its read-only dictionary loader. An attacker can induce a victim to load a malicious dictionary, potentially causing denial of service and code execution. The vulnerability is caused by a flawed computation of capacity check in String::reserve() in common/string.hpp. ReadOnlyDict::load() in modules/speller/default/readonly_ws.cpp passes unvalidated 32-bit size fields from a .rws dictionary header into this path. Defenders should prioritize verifying GNU Aspell versions and updating to 0.60.8.3 or later.

Defensive priority

Defenders should prioritize verifying GNU Aspell versions and updating to 0.60.8.3 or later. They should also restrict loading untrusted dictionaries.

Recommended defensive actions

• Verify GNU Aspell versions and update to 0.60.8.3 or later
• Restrict loading untrusted dictionaries
• Monitor for suspicious dictionary loading activity
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability. However, the exact first vulnerable version of GNU Aspell is not known. The vulnerability is caused by a flawed computation of capacity check in String::reserve() in common/string.hpp. ReadOnlyDict::load() in modules/speller/default/readonly_ws.cpp passes unvalidated 32-bit size fields from a .rws dictionary header into this path. Defenders should verify GNU Aspell versions and update to 0.60.8.3 or later. They should also restrict loading untrusted dictionaries.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.