CVE-2026-128137: nltk · Link Following
Affects nltkSource CVE Database V5
Not known to be exploited · CVSS 5.5 Medium : upgrade to 3.10.4 when convenient.
Data as of 19 Nov 2026, 18:36 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:L/UI:N/S:U/C:H/I:N/A:NExploitation 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 vulnerability is fixed by enforcing path security to restrict file access within a global allowed root. No other mitigation is required as the fix addresses the root cause.
Description
NLTK versions from 3.9.4 up to but not including 3.10.4 contain a vulnerability where corpus-reader path pointers and view methods do not consistently resolve intermediate directory symlinks within the reader's scoped root. This allows a local attacker who can create such symlinks to access and disclose files outside the intended corpus root. The issue is fixed in version 3.10.4, which enforces path security to restrict file access within a global allowed root.