CVE-2026-128137
A linked directory could lead NLTK corpus views outside their scoped root
NLTK project · Natural Language Toolkit · corpus reader
First documented disclosure · Review checkpoint
Summary
A corpus view could read data from outside the directory that the application had authorized.
Severity and exploitation evidence
Medium · 5.5/10 · CVSS 3.1. Severity source.
Exploitation not established: The NLTK advisory describes the vulnerability and its preconditions. The reviewed sources identify no malicious use.
Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.
How the weakness works
Some corpus views opened paths without rechecking containment after resolving intermediate symbolic links.
Conditions required
An attacker can influence a directory link inside a corpus the application reads.
Potential impact
A corpus reader could expose files outside the intended corpus directory, subject to the application’s permissions.
Affected versions and configurations
3.9.4 - 3.10.3
Fix and mitigation status
3.10.4.
Practical next steps
Upgrade to NLTK 3.10.4 or a later fixed release.
Operating lesson
Store corpora in directories other accounts cannot modify and validate resolved paths.
Evidence and limits
The issue-specific patch was public by 2026-08-17. The fixed release shipped October 21. The November 15 maintainer advisory supplies the identifier and affected versions. This is a historical addition.
Sources
- NLTK public patch for corpus reader
Primary source ·
- NLTK 3.10.4 release notes
Primary source ·
- NLTK advisory GHSA-g58v-j9g9-5gfg
Primary source ·