Security Digest · Vulnerability record

CVE-2026-78683: NLTK: Unsafe Pickle Deserialization in TransitionParser Allows Remote Code Execution

NLTK before 3.10.0 (affected versions

CVSS 9.4 Critical EPSS 0.5% · p43

Should you act?

Critical and remotely reachable

No known exploitation yet, but it is network-reachable without credentials. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

  • Not in CISA KEV, but CISA’s SSVC assessment records a public proof-of-concept, so attack code exists.
  • EPSS 0.5%, percentile 43: FIRST’s model estimates a 0.5% chance of exploitation activity in the next 30 days, higher than 43% of all scored CVEs (low). EPSS is a probability, not a verdict.
  • Only applies if your dependency tree includes nltk (PyPI) <= 3.9.4, fixed in 3.10.0. Check your lockfile, including transitive dependencies.

What it is

NLTK before 3.10.0 (affected versions

From the GitHub advisory

Summary

The NLTK library's TransitionParser.parse() method deserializes model files using pickleload() with the default restricted=False parameter, allowing arbitrary Python code execution when loading a malicious model file. The library provides a RestrictedUnpickler class for safe deserialization, but it is never used by production code paths, leaving the vulnerability unpatched.

Root Cause

File: nltk/parse/transitionparser.py (lines 542-557)

The parse() method calls pickleload(f) without restricted=True, routing through WarningUnpickler which inherits from pickle.Unpickler and does NOT override findclass(). This allows arbitrary class/function resolution during unpickling, enabling RCE via standard pickle gadgets (e.g., os.system, subprocess.Popen).

Weakness type: CWE-502.

Product: nltk (PyPI) · Assigned by: VulnCheck · Published: 2026-08-25

Affected and fixed versions

EcosystemPackageVulnerableFirst fixed
PyPInltk<= 3.9.43.10.0
VendorProductAffected versions (per CVE record)
nltknltk< 3.10.0

Severity scores

Scored byCVSSScoreVector
VulnCheck4.09.4 CriticalCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
VulnCheck3.19.6 CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
GitHub4.09.4 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
  • Attack vector: network (remotely reachable)
  • Attack complexity: low
  • Attack requirements: none
  • Privileges required: none (no login)
  • User interaction: passive

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

  • CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
  • CISA SSVC assessment: exploitation poc, automatable no, technical impact total.
  • FIRST EPSS (model of 2026-10-21): 0.51% probability of exploitation activity in the next 30 days; percentile 43.

Timeline

  • — CVE record last updated
  • — CVE record published by VulnCheck
  • — GitHub-reviewed advisory GHSA-rhp5-r9x4-f5g2 published (critical)

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vendor and project advisories, patches

  1. GitHub Security Advisory (GHSA-rhp5-r9x4-f5g2) github.com

Vulnerability records

  1. GitHub Advisory GHSA-rhp5-r9x4-f5g2 github.com
  2. CVE.org record CVE-2026-78683 cve.org
  3. NVD entry CVE-2026-78683 nvd.nist.gov

Other references from the CVE record and advisory

  1. VulnCheck Advisory: NLTK before 3.10.0 Remote Code Execution via Unsafe Pickle Deserialization vulncheck.com
  2. github.com github.com
  3. github.com github.com
  4. github.com github.com
  5. github.com github.com

Critical PyPI advisories · Today’s Security Digest