Skip to main content
Menu
CVEs

NLTK file disclosure in corpus-reader methods

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

5.5MediumCNA
Exploited
No known exploitation
Fix
Fixed in 3.10.4
Who is exposed
Not reported

Summary

NLTK, the Natural Language Toolkit, has a flaw in its corpus-reader view methods that lets a local attacker with low privileges read files outside the corpus root, and no user action is needed. By placing a symlink in an intermediate directory, the attacker can make the abspaths or words methods reach a readable file elsewhere on the system and disclose its contents.

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 until 3.10.4, NLTK corpus-reader path pointers and view methods validate a requested relative path without consistently resolving intermediate directory symlinks against the reader's scoped root. A local attacker who can place such a symlink can make abspaths or words reach a readable file outside the corpus root and disclose its contents. On releases with pathsec enforcement, the file must remain inside a global NLTK allowed root; version 3.9.4 has enforcement disabled and permits a broader escape. This issue is fixed in version 3.10.4.

What to do

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-128137 (NLTK corpus-reader view methods bypass the scoped root sandbox via intermediate-directory symlinks), 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-128137 (entry last updated 2026-11-19):
Affected:
- nltk nltk: from 3.9.4, fixed in 3.10.4
Fixed versions: 3.10.4.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-128137 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-128137 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-g58v-j9g9-5gfg
- https://github.com/nltk/nltk/pull/3761
- https://github.com/nltk/nltk/commit/9f7cf06b4af4ca5c65381ed0abc17e989dc54400
- 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-128137
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-128137"}.

Affected versions

cve.now Index

6Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure?/25Unknown. No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity5.5/10CVSS 5.5
  • No patch0/5No signal

What would change the score

  • Would score about 61 if added to CISA KEV
  • Would score about 56 if CISA's SSVC rates exploitation active
  • Would score about 28 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Evidence 6

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · nltk/nltk · Advisory GHSA-g58v-j9g9-5gfg
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-128137
RecordNVD · CVE-2026-128137
Other links 3
RepositoryGitHub · nltk/nltk · Pull request #3761
RepositoryGitHub · nltk/nltk · Commit 9f7cf06b
RepositoryGitHub · nltk/nltk · Release v3.10.4

Questions about CVE-2026-128137

Is CVE-2026-128137 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

Which versions are affected by CVE-2026-128137?

nltk: from 3.9.4 before 3.10.4.

Source: cve.now feed data

How do I fix CVE-2026-128137?

Upgrade to a fixed version: 3.10.4.

Source: cve.now feed data

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