CVE-2026-128136: nltk · Deserialization of Untrusted Data
Affects nltkSource CVE Database V5
Not known to be exploited · CVSS 6.1 Medium : upgrade to 3.10.4 when convenient.
Data as of 19 Nov 2026, 18:11 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 6.1 |
|---|
- Patch
- Available – fixed in 3.10.4
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:L/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 deserialization vulnerability is fixed. Avoid loading pickle files from untrusted sources. Since an official fix is available, applying the update is the recommended mitigation.
Description
NLTK versions from 3.10.0 up to but not including 3.10.4 contain a deserialization vulnerability where crafted pickle files can exploit dangerous NumPy globals to perform unauthorized file read or write operations. This allows attackers to invoke functions like recfromtxt to read local files or open_memmap to create or truncate files when loading untrusted models. The issue is resolved in version 3.10.4.