CVE-2026-129226: nltk · Uncontrolled Recursion
Affects nltkSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium : upgrade to 3.10.4 when convenient.
Data as of 19 Nov 2026, 17:51 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 5.3 |
|---|
- Patch
- Available – fixed in 3.10.4
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:LExploitation 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 NLTK to version 3.10.4 or later, where this uncontrolled recursion vulnerability is fixed. No other mitigations are indicated.
Description
NLTK versions prior to 3.10.4 contain an uncontrolled recursion vulnerability in the semantic-logic read_type parser. This flaw allows an attacker to supply a type string with excessive nesting, causing a RecursionError and aborting the current worker process. The issue is resolved in version 3.10.4.
References
- github.com/nltk/nltk/security/advisories/GHSA-w3pv-xfw4-ghr7 (opens in a new tab)
- github.com/nltk/nltk/pull/3885 (opens in a new tab)
- github.com/nltk/nltk/commit/2f4f0d47e2c452c89cabc2a5f761332d51066ea8 (opens in a new tab)
- github.com/nltk/nltk/commit/a8036c5e7f820ac09c96b969d6e7f19bfa6e6aeb (opens in a new tab)
- github.com/nltk/nltk/releases/tag/v3.10.4 (opens in a new tab)