CVE-2026-128135: ZIP package extraction follows in-root hardlinks and overwrites files outside the NLTK data root
Affects nltkSource GCVE Database
Not known to be exploited · CVSS 7.1 High : upgrade to 3.10.4 soon.
Data as of 20 Nov 2026, 01:50 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 7.1 |
|---|
- Patch
- Available – fixed in 3.10.4
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 19 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.
What to do
Upgrade nltk to 3.10.4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| PyPInltk | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix for this vulnerability is available in NLTK version 3.10.4. Users should upgrade to version 3.10.4 or later to remediate this issue. Until upgraded, ensure that unprivileged users cannot write to shared or predictable NLTK data roots to prevent pre-planting of hardlinks. Kernel-level hardlink protections (e.g., fs.protected_hardlinks) should be enabled to reduce risk. No other mitigations are documented or necessary once patched.
Description
NLTK versions from 3.9.4 up to but not including 3.10.4 contain a vulnerability in the nltk.pathsec.ZipFile archive extraction component. The extraction process fails to properly check for hardlinks inside the extraction root, allowing a local attacker with write access to the NLTK data root to pre-plant a hardlink that points outside the root. When NLTK extracts a package, it overwrites the target of that hardlink outside the data root, leading to arbitrary file truncation and overwriting. This can result in complete integrity loss of the targeted file. The vulnerability requires local access and suitable permissions to create hardlinks and is mitigated by a fix released in version 3.10.4.
References
- github.com/nltk/nltk/security/advisories/GHSA-wr3g-j6qj-xpgh (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-128135 (opens in a new tab)
- github.com/nltk/nltk/pull/3753 (opens in a new tab)
- github.com/nltk/nltk/commit/0e9898b7615b4ab3b023e868212316a489ece4f0 (opens in a new tab)
- github.com/nltk/nltk/commit/cf12a5e6a439fe1d722acd53d4309911faaaaf78 (opens in a new tab)
- github.com/nltk/nltk (opens in a new tab)
- github.com/nltk/nltk/releases/tag/v3.10.4 (opens in a new tab)