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.
CVE-2026-71513
Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-22. a secondary CVSS source baseline 8.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.8
- EG Score
- 8.8(high)
- EG Risk
- 40(Track)EG Risk 40/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity88% × 45%Exploitation1% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 53%
- KEV
- Not listed
Published
August 22, 2026
Last Modified
August 27, 2026
Advisory Details (4)
Auto-updated Aug 22, 2026NLTK 3.10.0 through 3.10.2 Remote Code Execution via AllowlistUnpickler Dotted-Name Bypass | Advisories | VulnCheck
https://www.vulncheck.com/advisories/nltk-through-remote-code-execution-via-allowlistunpickler-dotted-name-bypassnltk/nltk/picklesec.py at v3.10.2 · nltk/nltk · GitHub
https://github.com/nltk/nltk/blob/v3.10.2/nltk/picklesec.py#L119-L124commit c3e37113742a (nltk/nltk)
Patch available: nltk/nltk v3.10.3-rc1 (contains commit c3e37113742a)
https://github.com/nltk/nltk/commit/c3e37113742a1ebeeb4f2ca58941f320f98805eaVendor Advisories for CVE-2026-71513(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 33× in last 7d / 33× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-29 05:41 UTCEG score recompute
- 2026-08-29 05:40 UTCGHSA enrichment
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-28 18:05 UTCGHSA enrichment
- 2026-08-28 05:16 UTCGHSA enrichment
- 2026-08-27 17:37 UTCEG score recompute
- 2026-08-27 17:37 UTCGHSA enrichment
- 2026-08-27 17:17 UTCEG score recompute
- 2026-08-27 17:17 UTCGHSA enrichment
- 2026-08-27 14:22 UTCGHSA enrichment
- 2026-08-27 02:46 UTCGHSA enrichment
- 2026-08-26 15:11 UTCEG score recompute
- 2026-08-26 15:11 UTCGHSA enrichment
- 2026-08-26 14:47 UTCEPSS rescore
- 2026-08-26 03:35 UTCGHSA enrichment
- 2026-08-25 15:59 UTCEG score recompute
- 2026-08-25 15:59 UTCGHSA enrichment
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 04:23 UTCEG score recompute
- 2026-08-25 04:23 UTCGHSA enrichment
- 2026-08-25 04:10 UTCEG score recompute
- 2026-08-25 04:10 UTCGHSA enrichment
- 2026-08-25 00:19 UTCEG score recompute
- 2026-08-25 00:19 UTCGHSA enrichment
- 2026-08-24 12:43 UTCEG score recompute
Show 8 moreShow fewer
- 2026-08-24 12:43 UTCGHSA enrichment
- 2026-08-24 01:08 UTCGHSA enrichment
- 2026-08-23 13:33 UTCGHSA enrichment
- 2026-08-23 01:57 UTCEG score recompute
- 2026-08-23 01:57 UTCGHSA enrichment
- 2026-08-22 14:22 UTCEG score recompute
- 2026-08-22 13:46 UTCEG score recompute
- 2026-08-22 13:45 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-71513?
When was CVE-2026-71513 disclosed?
Is CVE-2026-71513 actively exploited?
What is the CVSS score of CVE-2026-71513?
How do I remediate CVE-2026-71513?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-71513
Is Your Infrastructure Affected by CVE-2026-71513?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.