Skip to main content
Menu
CVEs

NLTK file overwrite via hardlinks in ZIP package extraction

Affects nltk 3.9.4 through 3.10.3 installed from pip. Fixed in 3.10.4.

CVE-2026-128135Published November 19, 2026, updated

7.1HighCNA
Exploited
No known exploitation
Fix
Fixed in 3.10.4
Who is exposed
Specific setups only

Summary

NLTK's ZIP package extraction can follow a hardlink inside the NLTK data root whose other link points outside it. A local attacker with low privileges and no user action needed can use this to overwrite files outside the data root, which harms integrity and availability.

Written by a model

Original description

NLTK (Natural Language Toolkit) is a suite of open source Python modules, data sets, and tutorials supporting research and development in Natural Language Processing. From 3.9.4 to 3.10.3, NLTK ZIP package extraction can write through an existing in-root hardlink whose other link points outside the NLTK data root. A local attacker who can prepare the extraction target can cause a package member write to overwrite an out-of-root file, violating the pathsec containment boundary and affecting integrity and availability. This issues is fixed in version 3.10.4.

Who should check

Teams running nltk 3.9.4 through 3.10.3 with nltk.download() or the downloader on shared or predictable data roots such as ~/nltk_data or group-writable /usr/share/nltk_data.

“Affected versions >= 3.9.4, <= 3.10.3”

github.com

What to do

  1. Check whether your setup matches what the bug needs.

    Affected versions 3.9.4 through 3.10.3 of the nltk package (pip). A pre-existing in-root hardlink must sit at the member path the package will write, and the attacker must be able to write inside the shared or predictable NLTK data root. Practical exploitation requires kernel hardlink protection (fs.protected_hardlinks) to be disabled, or the outside target to be one the attacker is permitted to hardlink.
  2. Upgrade to a fixed version: 3.10.4.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-128135 (NLTK: ZIP package extraction follows in-root hardlinks and overwrites files outside the NLTK data root), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-128135 (entry last updated 2026-11-19):
Affected:
- nltk nltk: from 3.9.4, fixed in 3.10.4
Fixed versions: 3.10.4.
Conditions (all must be true for the bug to be hit):
- Affected versions 3.9.4 through 3.10.3 of the nltk package (pip). (source: https://github.com/nltk/nltk/security/advisories/GHSA-wr3g-j6qj-xpgh)
- A pre-existing in-root hardlink must sit at the member path the package will write, and the attacker must be able to write inside the shared or predictable NLTK data root. (source: https://github.com/nltk/nltk/security/advisories/GHSA-wr3g-j6qj-xpgh)
- Practical exploitation requires kernel hardlink protection (fs.protected_hardlinks) to be disabled, or the outside target to be one the attacker is permitted to hardlink. (source: https://github.com/nltk/nltk/security/advisories/GHSA-wr3g-j6qj-xpgh)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, low-privilege login, no user action.
CISA KEV: CVE-2026-128135 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-128135 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/nltk/nltk/security/advisories/GHSA-wr3g-j6qj-xpgh
- https://github.com/nltk/nltk/pull/3753
- https://github.com/nltk/nltk/commit/0e9898b7615b4ab3b023e868212316a489ece4f0
- https://github.com/nltk/nltk/commit/cf12a5e6a439fe1d722acd53d4309911faaaaf78
- https://github.com/nltk/nltk/releases/tag/v3.10.4
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-128135
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-128135"}.

Affected versions

cve.now Index

12Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure5/25Specific setups only
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.1/10CVSS 7.1
  • No patch0/5No signal

What would change the score

  • Would score about 62 if added to CISA KEV
  • Would score about 57 if CISA's SSVC rates exploitation active
  • Would score about 22 if CISA's SSVC rates it automatable

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 7

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · nltk/nltk · Advisory GHSA-wr3g-j6qj-xpgh
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-128135
RecordNVD · CVE-2026-128135
Other links 4
RepositoryGitHub · nltk/nltk · Pull request #3753
RepositoryGitHub · nltk/nltk · Commit 0e9898b7
RepositoryGitHub · nltk/nltk · Commit cf12a5e6
RepositoryGitHub · nltk/nltk · Release v3.10.4

Questions about CVE-2026-128135

Is CVE-2026-128135 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

When NLTK extracts a ZIP package, it can follow a pre-existing hardlink inside the NLTK data root and truncate and overwrite a file outside that root. A local user who can write inside a shared or predictable NLTK data root can cause this.

Source: github.com

Which versions are affected by CVE-2026-128135?

nltk: from 3.9.4 before 3.10.4.

Source: cve.now feed data

Am I affected, and how do I check?

The issue affects nltk versions 3.9.4 through 3.10.3 installed with pip. To check an installation, run pip show nltk or python -c "import nltk; print(nltk.__version__)". The advisory also depends on the kernel setting fs.protected_hardlinks, which can be read with sysctl fs.protected_hardlinks.

Source: github.com

How do I fix CVE-2026-128135?

Upgrade nltk to 3.10.4, the first fixed version in the product range. No vendor patch identifiers are given in the facts.

Source: github.com

No corrections so far. Something wrong on this page? Report an error.