CVE-2026-33236

8.1

NLTK Project · Natural Language Toolkit (NLTK)

The NLTK downloader fails to validate input attributes when processing remote XML index files, allowing unauthenticated attackers to perform path traversal and arbitrary file operations.

Executive summary

An unauthenticated path traversal vulnerability in the NLTK library allows remote attackers to perform unauthorized file creation and overwriting on the host system.

Vulnerability

This vulnerability is a path traversal flaw (CWE-22) in the NLTK downloader. An unauthenticated attacker can supply a malicious remote XML index file to manipulate the subdir and id attributes, enabling arbitrary file creation or overwriting outside the intended directory.

Business impact

The ability to write or overwrite arbitrary files on a server poses a significant risk to system integrity and availability. An attacker could potentially overwrite critical configuration files or system binaries to facilitate remote code execution or cause a denial of service. Given the CVSS score of 8.1, this vulnerability is classified as High severity and requires prompt attention to prevent unauthorized system modification.

Remediation

Immediate Action: Users should restrict the NLTK downloader to trusted sources only and monitor for any suspicious file system activity until a formal package update is released. Review the provided GitHub security advisory for status updates regarding the availability of a patched version.

Proactive Monitoring: Security teams should audit application logs for unexpected file write operations or attempts to access directories outside of the designated NLTK data path.

Compensating Controls: Implement strict egress filtering to prevent the application from connecting to untrusted or unauthorized XML index servers.

Exploitation status

Public Exploit Available: No (No confirmed weaponized exploit or public proof-of-concept repository identified).

Analyst recommendation

Due to the potential for arbitrary file modification, organizations utilizing the NLTK library must treat this vulnerability with high priority. While a formal patch version is pending, administrators should immediately implement network-level controls to prevent the application from fetching data from untrusted XML sources. Once a remediated version is published by the vendor, it should be deployed across all environments without delay to fully mitigate this risk.

More NLTK Project CVEs

Sources