NLTK: Uncontrolled recursion
Affects nltkSource GCVE Database
Not known to be exploited · CVSS 5.5 Medium : upgrade to 3.10.4 when convenient.
Data as of 20 Nov 2026, 00:29 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 5.5 |
|---|
- Patch
- Available – fixed in 3.10.4
CVSS:3.1/AV:L/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 19 Nov 2026.
What to do
Upgrade nltk to 3.10.4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| PyPInltk | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in NLTK version 3.10.4 that addresses this issue. Users should upgrade to version 3.10.4 or later. Until upgraded, applications should avoid loading untrusted WordNet corpus files or implement exception handling for RecursionError around calls to the affected methods. No other mitigations are specified.
Description
NLTK versions prior to 3.10.4 contain a vulnerability in four hypernym-walking methods of the WordNet Synset class that perform recursive graph traversal without cycle detection or depth limits. An attacker who can supply a malicious WordNet corpus file with cyclic or excessively deep hypernym pointer graphs can cause these methods to recurse indefinitely, resulting in a RecursionError that aborts the traversal and potentially crashes the application process. This vulnerability impacts availability only and requires no special privileges beyond loading attacker-controlled corpus data. The issue is fixed in NLTK version 3.10.4.
References
- github.com/nltk/nltk/security/advisories/GHSA-53pg-5qp8-mhvr (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-129230 (opens in a new tab)
- github.com/nltk/nltk/pull/3895 (opens in a new tab)
- github.com/nltk/nltk/commit/34adf1ee425b5c817d2a88c674bac68672e3ab26 (opens in a new tab)
- github.com/nltk/nltk (opens in a new tab)
- github.com/nltk/nltk/releases/tag/v3.10.4 (opens in a new tab)