NLTK
NLTK before 3.10.0 Remote Code Execution via Unsafe Pickle Deserialization
NLTK before 3.10.0 (affected versions <=3.9.4) contains an unsafe pickle deserialization vulnerability in the TransitionParser.parse() method (nltk/parse/transitionparser.py). The method calls pickle_load() with the default restricted=False, routing deserialization through WarningUnpickler, which does not override find_class() and therefore permits arbitrary class resolution. When an application loads an attacker-crafted model file, embedded pickle gadget chains execute arbitrary Python code with the privileges of the user running the application. NLTK provides a RestrictedUnpickler for safe deserialization, but it is not used by production code paths. Fixed in 3.10.0.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 3.10.0
Fixed in 3.10.0
Mitigation
Upgrade nltk to 3.10.0 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 informational
Informational 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| kinryulabs/research-pocs | 20 Sep 2026 +27 d | 0 | Informational · list |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.