CVE-2026-129223: nltk · Uncontrolled Recursion
Affects nltkSource CVE Database V5
Not known to be exploited · CVSS 7.5 High : upgrade to 3.10.4 soon.
Data as of 19 Nov 2026, 18:21 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 7.5 |
|---|
- 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: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 NLTK to version 3.10.4 or later, where this uncontrolled recursion issue is fixed. If upgrading is not immediately possible, avoid loading untrusted or custom WordNet-format lexical resources that could contain excessively deep relation graphs.
Description
NLTK versions prior to 3.10.4 contain an uncontrolled recursion vulnerability in the WordNet Synset.tree and acyclic_tree functions. These functions traverse relation graphs recursively without a depth limit, which can lead to exceeding Python's recursion limit and crashing the process. Exploitation requires loading a maliciously crafted WordNet-format lexical resource, as the default NLTK WordNet corpus does not trigger this issue. The vulnerability is fixed in version 3.10.4.