cve.bz

CVE-2026-62384 nltk nltk: Path traversal

8.7 highExploit referenceEPSS 0.7%Fix available

High (8.7) in nltk nltk. EPSS 0.7% 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 sandbox bypass in FramenetCorpusReader that allows attackers to read arbitrary XML files outside the corpus root. Attackers can place symlinks with names containing no path separators inside the corpus subdirectory, which pass the path validation guard and are resolved to files outside the intended corpus root when accessed via frame_by_name(), _lu_file(), or doc() methods.

Severity

CVSS 4.0

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

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
0.7% (unchanged from 0.7% a week ago; 0.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 52nd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · 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-62384 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-62384?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-62384?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-62384 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-f833-7jw8-xwrvPyPInltk>=3.10.0 <3.10.23.10.2
PYSEC-2026-3789PyPInltk>=3.10.0 <3.10.23.10.2

Linux distributions

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

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

Red Hat's statement

A path traversal vulnerability exists in NLTK's FramenetCorpusReader component via symbolic links. When resolving corpus files using methods like frame_by_name(), _lu_file(), or doc(), path validation checks fail to restrict symlinks containing no path separators within subdirectories. An attacker capable of placing crafted symlinks in a corpus directory can read arbitrary XML files outside the intended corpus root. Confidentiality is impacted within the context of the running application, though standard Linux discretionary access controls and container boundaries restrict arbitrary file access beyond the process's effective permissions.

Red Hat's mitigation

Restrict write permissions on NLTK corpus subdirectories to prevent unauthorized symlink creation, or sanitize input paths to prevent FramenetCorpusReader from loading untrusted corpus files containing unresolved symbolic links.

ProductPackageStateAdvisory
Red Hat OpenShift AI 2.25rhoai/odh-llama-stack-core-rhel9:1791873747Fixed 2026-10-21RHSA-2026:87410
Red Hat OpenShift AI 2.25rhoai/odh-pipeline-runtime-pytorch-llmcompressor-cuda-py312-rhel9:1791867208Fixed 2026-10-21RHSA-2026:87410
Red Hat OpenShift AI 2.25rhoai/odh-ta-lmes-job-rhel9:1791553527Fixed 2026-10-21RHSA-2026:87410
Red Hat OpenShift AI 2.25rhoai/odh-workbench-jupyter-pytorch-llmcompressor-cuda-py312-rhel9:1791867189Fixed 2026-10-21RHSA-2026:87410
Red Hat OpenShift AI 3.3rhoai/odh-llama-stack-core-rhel9:1789121286Fixed 2026-09-30RHSA-2026:73987
Red Hat OpenShift AI 3.4rhoai/odh-llama-stack-core-rhel9:1790958470Fixed 2026-10-19RHSA-2026:84734
Red Hat OpenShift AI 3.4rhoai/odh-ta-lmes-job-rhel9:1791470318Fixed 2026-10-19RHSA-2026:84734
Red Hat OpenShift AI 3.4rhoai/odh-trustyai-garak-lls-provider-dsp-rhel9:1791785804Fixed 2026-10-19RHSA-2026:84734
Red Hat OpenShift AI 3.4rhoai/odh-trustyai-nemo-guardrails-server-rhel9:1791556128Fixed 2026-10-19RHSA-2026:84734
Red Hat OpenShift AI 3.5rhoai/odh-ta-lmes-job-rhel9:1788935863Fixed 2026-09-21RHSA-2026:69539
Exploit Intelligenceexploit-intelligence-tech-preview/vulnerability-analysis-rhel9Will not fix
Lightspeed Corelightspeed-core/lightspeed-stack-rhel9Affected
Lightspeed Corelightspeed-core/rag-tool-cpu-rhel9Affected
Lightspeed Corelightspeed-core/rag-tool-cuda-12.9-rhel9Affected
OpenShift Lightspeedopenshift-lightspeed/lightspeed-ocp-rag-rhel9Not affected
OpenShift Lightspeedopenshift-lightspeed/lightspeed-service-api-rhel9Affected
OpenShift Lightspeedopenshift-lightspeed-tech-preview/lightspeed-rag-tool-rhel9Not affected
OpenShift Lightspeedopenshift-lightspeed/lightspeed-service-api-rhel9Not affected
Red Hat Ansible Automation Platform 2ansible-automation-platform-25/lightspeed-chatbot-rhel8Will not fix
Red Hat OpenShift AI (RHOAI)rhoai/odh-ogx-core-rhel9Affected
2 more in the JSON and on Red Hat's page.

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

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