cve.bz

CVE-2026-62383 nltk nltk: Path traversal

6.8 mediumExploit referenceEPSS 0.2%Fix available

Medium (6.8) in nltk nltk. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in nltk 3.10.2.

On this page
nltk versions before 3.10.2 contain a symlink-based arbitrary file read vulnerability in IPIPANCorpusReader methods that bypass nltk.pathsec validation entirely. Attackers can place a symlink in the corpus root directory and read arbitrary files accessible to the process by calling channels(), domains(), categories(), or fileids() methods with the symlink filename.

Severity

CVSS 4.0

6.8 medium
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

CVSS 3.1

5.5 medium
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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; 8th 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-26. 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-62383 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-62383?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-62383?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-62383 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.10.0 before 3.10.2

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-3hhw-38pf-pxj6PyPInltk>=3.10.0 <3.10.23.10.2
PYSEC-2026-3726PyPInltk>=3.10.0 <3.10.23.10.2

Linux distributions

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

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 Moderate.

Red Hat's statement

The `nltk` library is vulnerable to information disclosure, allowing an attacker with local access and low privileges to read arbitrary files. This occurs if an attacker can place a symlink within the `nltk` corpus root directory, bypassing path validation and enabling access to sensitive data with the permissions of the running process.

Red Hat's mitigation

To mitigate this vulnerability, restrict write access to the `IPIPANCorpusReader` corpus root directory. Ensure that only trusted users or processes have permissions to create or modify files within this directory. This prevents an attacker from placing malicious symlinks that could lead to arbitrary file disclosure.

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-62383.

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