NLTK
NLTK before 3.10.3 Remote Code Execution via Unsafe Pickle Deserialization
NLTK versions before 3.10.3 contain a remote code execution vulnerability in allowlisted pickle loaders that trust entire module namespaces instead of specific safe callables. Attackers can craft malicious pickle payloads invoking dangerous in-namespace functions like ReppTokenizer._execute and numpy.f2py.crackfortran.myeval through pickle REDUCE to execute arbitrary commands during model or tokenizer artifact loading.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 3.10.3
Fixed in 3.10.3
Mitigation
Upgrade nltk to 3.10.3 or later.
References
- Vendor advisory github.com/nltk/nltk/security/advisories/GHSA-…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.1 pending
Pending 1
| Repository | Created | Found by us | Stars | Assessment |
|---|---|---|---|---|
| federiconbaez/cortex9-nltk-pickle-allowlist-prefix-model | 9 Nov 2026 +76 d | 14 Nov 2026 | 0 | Pending
Flags · score 15
Below the suspicion threshold (50); does not change the assessment. |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.