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.
CVE-2026-78683
Score 9.6 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-25. a secondary CVSS source baseline 9.6; 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
- 9.6
- EG Score
- 9.6(high)
- EG Risk
- 59(Track*)EG Risk 59/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 computedSeverity96% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Watch closely — could escalate to Attend. - EPSS PROB
- 0%
- EPSS %ILE
- 20%
- KEV
- Not listed
Published
August 25, 2026
Last Modified
August 28, 2026
Advisory Details (2)
Auto-updated Aug 28, 2026[CWE-502] Unsafe Pickle Deserialization in TransitionParser Allows Remote Code Execution · Advisory · nltk/nltk · GitHub
Affected: 3.10.0+.
https://github.com/nltk/nltk/security/advisories/GHSA-rhp5-r9x4-f5g2NLTK before 3.10.0 Remote Code Execution via Unsafe Pickle Deserialization | Advisories | VulnCheck
https://www.vulncheck.com/advisories/nltk-before-remote-code-execution-via-unsafe-pickle-deserializationVendor Advisories for CVE-2026-78683(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 37× in last 7d / 37× 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 04:31 UTCGHSA enrichment
- 2026-08-29 00:18 UTCEG score recompute
- 2026-08-29 00:18 UTCGHSA enrichment
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-28 19:08 UTCGHSA enrichment
- 2026-08-28 16:23 UTCGHSA enrichment
- 2026-08-28 11:51 UTCGHSA enrichment
- 2026-08-28 07:41 UTCGHSA enrichment
- 2026-08-28 03:30 UTCGHSA enrichment
- 2026-08-27 23:21 UTCGHSA enrichment
- 2026-08-27 19:12 UTCGHSA enrichment
- 2026-08-27 15:01 UTCGHSA enrichment
- 2026-08-27 10:51 UTCGHSA enrichment
- 2026-08-27 06:40 UTCGHSA enrichment
- 2026-08-27 02:05 UTCGHSA enrichment
- 2026-08-26 21:55 UTCGHSA enrichment
- 2026-08-26 17:46 UTCEG score recompute
- 2026-08-26 17:46 UTCGHSA enrichment
- 2026-08-26 14:47 UTCEPSS rescore
- 2026-08-26 13:18 UTCGHSA enrichment
- 2026-08-26 09:08 UTCGHSA enrichment
- 2026-08-26 04:55 UTCGHSA enrichment
- 2026-08-26 00:46 UTCGHSA enrichment
- 2026-08-25 20:37 UTCGHSA enrichment
- 2026-08-25 16:24 UTCEG score recompute
Show 12 moreShow fewer
- 2026-08-25 16:24 UTCGHSA enrichment
- 2026-08-25 15:30 UTCEG score recompute
- 2026-08-25 15:30 UTCGHSA enrichment
- 2026-08-25 14:49 UTCEG score recompute
- 2026-08-25 14:49 UTCGHSA enrichment
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 10:40 UTCGHSA enrichment
- 2026-08-25 06:30 UTCEG score recompute
- 2026-08-25 06:30 UTCGHSA enrichment
- 2026-08-25 02:19 UTCEG score recompute
- 2026-08-25 01:50 UTCEG score recompute
- 2026-08-25 01:50 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-502
- CVE-2017-10992EG 9.8EPSS p95CRITICAL
- CVE-2013-4521EG 9.8EPSS p90CRITICAL
- CVE-2014-1860EG 9.8CRITICAL
- CVE-2016-1000027EG 9.8EPSS p98CRITICAL
- CVE-2014-3699EG 9.8CRITICAL
- CVE-2017-10934EG 9.8CRITICAL
- CVE-2016-9498EG 9.8EPSS p97CRITICAL
- CVE-2016-9483EG 9.8CRITICAL
- CVE-2015-2020EG 9.8CRITICAL
- CVE-2017-15692EG 9.8EPSS p91CRITICAL
Frequently asked(5)
What is CVE-2026-78683?
When was CVE-2026-78683 disclosed?
Is CVE-2026-78683 actively exploited?
What is the CVSS score of CVE-2026-78683?
How do I remediate CVE-2026-78683?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-78683
Is Your Infrastructure Affected by CVE-2026-78683?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.