CVE-2026-33236: NLTK has a Downloader Path Traversal Vulnerability (AFO) - Arbitrary File Overwrite
NLTK (Natural Language Toolkit) is a suite of open source Python modules, data sets, and tutorials supporting research and development in Natural Language Processing. In versions 3.9.3 and prior, the NLTK downloader does not validate the `subdir` and `id` attributes when processing remote XML index files. Attackers can control a remote XML index server to provide malicious values containing path traversal sequences (such as `../`), which can lead to arbitrary directory creation, arbitrary file creation, and arbitrary file overwrite. Commit 89fe2ec2c6bae6e2e7a46dad65cc34231976ed8a patches the issue.
Security readout for executives and security teams
Plain-English summary
NLTK's downloader could be tricked by a malicious package index into writing files outside the intended download directory. The practical risk is unauthorized file creation or overwrite on systems where users or automation fetch NLTK data from an attacker-controlled or compromised index.
Executive priority
Treat as high priority for teams using NLTK in automated ML or data-processing pipelines. The issue can alter or destroy local files, but available evidence does not show active exploitation or remote compromise without user interaction.
Technical view
In NLTK 3.9.3 and prior, downloader handling of remote XML index metadata fails to validate subdir and id attributes. Path traversal values can cause arbitrary directory creation, arbitrary file creation, and arbitrary file overwrite. The issue is CWE-22 with CVSS 8.1 and is patched by commit 89fe2ec2c6bae6e2e7a46dad65cc34231976ed8a.
Likely exposure
Most exposed environments are Python development, research, ML, and CI systems using NLTK downloader with remote or mirrored index files. Exposure is lower where NLTK data is pinned, prepackaged, or fetched only from trusted sources.
Exploitation context
The CVSS vector shows network attack complexity is low but user interaction is required. The provided sources do not report CISA KEV listing or active exploitation. Exploitation depends on attacker control of the XML index source used by the downloader.
Researcher notes
Key review points are XML index trust boundaries and path normalization around subdir and id. The source bundle names the patch commit, but does not provide a fixed NLTK release number. Avoid assuming affected downstream packages beyond listed vendor advisories.
Mitigation direction
Upgrade NLTK when a vendor release containing the patch is available.
Apply vendor-provided fixed packages, including relevant Red Hat errata where applicable.
Avoid using untrusted or attacker-controlled NLTK downloader index sources.
Pin and verify NLTK data sources used by CI and production workflows.
Monitor the GitHub advisory and vendor channels for fixed version guidance.
Validation and detection
Inventory Python environments for nltk versions 3.9.3 and earlier.
Identify workflows invoking the NLTK downloader or fetching NLTK data dynamically.
Confirm downloader index URLs are trusted and not user-controlled.
Check vendor advisories for package status in managed distributions.
Verify patched code includes commit 89fe2ec2c6bae6e2e7a46dad65cc34231976ed8a or equivalent.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-22 · source CWE mapping
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.