cve.bz

CVE-2026-71514 nltk nltk: Path traversal

2.0 lowEPSS 0.2%Fix available

Low (2.0) in nltk nltk. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in nltk 3.10.3.

On this page
NLTK 3.9.4 through 3.10.2 contains a path traversal vulnerability in CrubadanCorpusReader. _load_lang_ngrams joins the corpus root with crubadan_code, the column-0 value read from the corpus table.txt mapping file, and opens the result with the builtin open() rather than the pathsec-validated opener, so os.path.join discards the root when that value is absolute and the read escapes the corpus directory without the containment check nltk.pathsec applies when ENFORCE is set. An attacker who controls a corpus package can disclose file contents outside the corpus root through lang_freq, limited to paths ending in -3grams.txt whose contents parse as token count lines.

Severity

CVSS 4.0

2.0 low
CVSS:4.0/AV:L/AC:H/AT:P/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

CVSS 3.1

3.3 low
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 7th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-08-24. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-71514 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-71514?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-71514?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-71514 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
nltkfrom 3.9.4 before 3.10.3

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-cv22-g7mw-8v73PyPInltk>=3.9.4 <3.10.33.10.3
PYSEC-2026-3790PyPInltk>=3.9.4 <3.10.33.10.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13nltkno fix listedDEBIAN-CVE-2026-71514
Debian14nltk3.10.3-1DEBIAN-CVE-2026-71514
Ubuntu26.10, Pro:14.04:LTS, Pro:16.04:LTS and 5 morenltkno fix listedUBUNTU-CVE-2026-71514

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Red Hat

Red Hat rates this Low.

Red Hat's statement

This Low impact vulnerability in NLTK's CrubadanCorpusReader allows for limited information disclosure via path traversal. Exploitation requires an attacker to provide a specially crafted corpus package, restricting the attack surface. The vulnerability is further limited to disclosing files ending in '-3grams.txt' that parse as token count lines, which reduces the overall risk.

ProductPackageStateAdvisory
Exploit Intelligenceexploit-intelligence-tech-preview/vulnerability-analysis-rhel9Not affected
Lightspeed Corelightspeed-core/lightspeed-stack-rhel9Not affected
Lightspeed Corelightspeed-core/rag-tool-cpu-rhel9Not affected
Lightspeed Corelightspeed-core/rag-tool-cuda-12.9-rhel9Not affected
OpenShift Lightspeedopenshift-lightspeed/lightspeed-ocp-rag-rhel9Not affected
OpenShift Lightspeedopenshift-lightspeed/lightspeed-service-api-rhel9Not affected
OpenShift Lightspeedopenshift-lightspeed-tech-preview/lightspeed-rag-tool-rhel9Not affected
Red Hat Ansible Automation Platform 2ansible-automation-platform-25/lightspeed-chatbot-rhel8Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-llama-stack-core-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-ogx-core-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-pipeline-runtime-pytorch-llmcompressor-cuda-py312-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-ta-lmes-job-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-trustyai-garak-lls-provider-dsp-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-trustyai-nemo-guardrails-server-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-workbench-jupyter-pytorch-llmcompressor-cuda-py312-rhel9Not affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-71514.

Attack patterns (CAPEC)

  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-126 Path Traversal Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON