CVE-2026-128140: nltk · Infinite Loop
Affects nltkSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium : upgrade to 3.10.4 when convenient.
Data as of 19 Nov 2026, 17:37 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 6.5 |
|---|
- Patch
- Available – fixed in 3.10.4
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 19 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Upgrade nltk to 3.10.4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| nltknltk | Affected
| Fixed in
|
AI-suggested
Upgrade to NLTK version 3.10.4 or later, where this infinite loop vulnerability has been fixed. No other mitigation is indicated.
Description
NLTK versions from 3.6.7 up to but not including 3.10.4 contain an infinite loop vulnerability in the nltk.downloader component. This occurs because the downloader does not track already visited collection nodes, allowing self-referencing or mutually referencing collection indexes to cause an infinite loop. This leads to unbounded queue and memory growth, resulting in a denial of service. The issue is fixed in version 3.10.4.