cve.bz

CVE-2026-109956 nltk nltk: Path traversal

8.3 highEPSS 0.3%Fix available

High (8.3) in nltk nltk. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in nltk 3.10.4.

On this page
NLTK through 3.10.3 contains a path traversal vulnerability in WekaClassifier that allows attackers to bypass nltk.pathsec containment by supplying unvalidated model paths. Attackers controlling the model_filename or model argument can make the weka JVM write files via -d or probe files via -l outside allowed data roots.

Severity

CVSS 4.0

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

CVSS 3.1

7.0 high
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:L
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 25th 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: no · Technical impact: partial, assessed 2026-10-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
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • nltk (PyPI): fixed in 3.10.4

Ask an AI about this CVE

Show the promptExplain CVE-2026-109956 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-109956?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-109956?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-109956 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
nltkthrough 3.10.3

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-j456-xh4h-cpf2PyPInltk<3.10.43.10.4

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14nltkno fix listedDEBIAN-CVE-2026-109956
Ubuntu26.10, Pro:14.04:LTS, Pro:16.04:LTS and 5 morenltkno fix listedUBUNTU-CVE-2026-109956

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

A moderate path traversal vulnerability was found in the Natural Language Toolkit (NLTK) WekaClassifier module, which affects Red Hat AI offerings that ship the nltk Python package, including Red Hat Lightspeed and OpenShift AI (RHOAI) components. The WekaClassifier does not validate the model_filename and model path arguments, so an attacker who can control these arguments can bypass the nltk.pathsec directory containment and cause the Weka JVM to write arbitrary files (via the -d option) or probe for existing files (via the -l option) outside of the allowed data directories. Successful exploitation requires an application to pass attacker-controlled paths to the WekaClassifier interface in an environment where the Weka JVM is available, which limits practical exposure; the impact is primarily high integrity loss through unauthorized file writes, with limited confidentiality and availability impact. While the upstream CVE record rates this flaw as Important, Red Hat classifies it as Moderate because exploitation depends on an application exposing the WekaClassifier interface to untrusted path input in a configured Weka environment. The affected Red Hat products are considered vulnerable, and a fix is being pursued through the responsible product teams.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat OpenShift AI 3.4rhoai/odh-ta-lmes-job-rhel9:1793001715Fixed 2026-10-29RHSA-2026:92510
Red Hat OpenShift AI 3.4rhoai/odh-trustyai-nemo-guardrails-server-rhel9:1793001780Fixed 2026-10-29RHSA-2026:92510
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-rhel9Affected
OpenShift Lightspeedopenshift-lightspeed/lightspeed-service-api-rhel9Affected
OpenShift Lightspeedopenshift-lightspeed-tech-preview/lightspeed-rag-tool-rhel9Affected
Red Hat Ansible Automation Platform 2ansible-automation-platform-25/lightspeed-chatbot-rhel8Out of support scope
Red Hat OpenShift AI (RHOAI)rhoai/odh-llama-stack-core-rhel9Affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-ogx-core-rhel9Affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-pipeline-runtime-pytorch-llmcompressor-cuda-py312-rhel9Affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-trustyai-garak-lls-provider-dsp-rhel9Affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-workbench-jupyter-pytorch-llmcompressor-cuda-py312-rhel9Affected

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

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