NLTK AllowlistUnpickler dotted-name validation bypass allows remote code execution
NLTK before 3.10.3 contains a remote code execution vulnerability in AllowlistUnpickler that validates only the pickle module string and not the global name, allowing attackers to resolve dotted names by attribute traversal to callables outside the allowlisted namespace. Attackers can craft untrusted transition-parser models that execute arbitrary commands when TransitionParser.parse loads the model through allowlisted_pickle_load.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2026-71513US | high8.8 | — | ||
NLTK before 3.10.3 contains a remote code execution vulnerability in AllowlistUnpickler that validates only the pickle module string and not the global name, allowing attackers to… | ||||
02
references
External citations — patches, advisories, analysis.
- https://github.com/nltk/nltkPACKAGE
- https://github.com/nltk/nltk/blob/v3.10.2/nltk/picklesec.py#L119-L124WEB
- https://github.com/nltk/nltk/commit/c3e37113742a1ebeeb4f2ca58941f320f98805eaWEB
- https://nvd.nist.gov/vuln/detail/CVE-2026-71513ADVISORY
- https://www.vulncheck.com/advisories/nltk-through-remote-code-execution-via-allowlistunpickler-dotted-name-bypassWEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan