CVE-2026-78683

published 25 Aug 2026 · updated 25 Aug 2026

NLTK before 3.10.0 Remote Code Execution via Unsafe Pickle Deserialization

9.6CriticalCVSS 9.6EPSS 1%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in 3.10.0.

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

Vendors, products and packages with version ranges

VendorProductVersionsFixed
nltk<3.10.03.10.0

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-78683 severity on Zeptric[![CVE-2026-78683](https://zeptric.io/badge/cve/CVE-2026-78683.svg)](https://zeptric.io/cve/CVE-2026-78683)