CVE-2026-128134 in NLTKinfo

Summary

by MITRE • 11/14/2026

NLTK (Natural Language Toolkit) is a suite of open source Python modules, data sets, and tutorials supporting research and development in Natural Language Processing. Prior to 3.10.4, nltk.parse.dependencygraph.dot2img resolves the Graphviz dot executable through PATH but invokes the resulting absolute executable without routing through spawn_trusted, so resolve_trusted_executable ownership and writability validation and safe_env loader environment scrubbing do not run. A local low-privileged attacker who can write to a directory on a POSIX victim's PATH can plant or replace dot, and code executes as the victim when dot2img is called directly or DependencyGraph.repr_svg renders a graph. The current-working-directory-only bare-name vector is blocked and is not this vulnerability; this issue is the residual writable absolute PATH element bypass after CVE-2026-78680. This issue is fixed in version 3.10.4.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Analysis

by VulDB Data Team • 11/15/2026

The Natural Language Toolkit, commonly known as NLTK, serves as a foundational suite of open-source Python modules and data sets for research and development in natural language processing. Within this ecosystem, the dependency graph parsing functionality provides utilities to visualize syntactic structures using external tools like Graphviz. A critical security flaw was identified in versions prior to 3.10.4 regarding how the dot2img function resolves and executes the Graphviz dot executable. The vulnerability stems from an insecure path resolution mechanism that bypasses established safety controls designed to prevent arbitrary code execution through environment manipulation or file system abuse.

The technical root cause lies in the method used to locate the external binary. Instead of strictly validating the resolved absolute path against a whitelist or ensuring it resides within trusted directories, the application resolves the executable name via the system PATH variable and then invokes the resulting absolute path directly. This approach fails to route the execution through the spawn_trusted helper function, which is responsible for enforcing ownership checks, writability validations, and environment scrubbing via safe_env loaders. Consequently, if an attacker can write to any directory listed in the victim's PATH environment variable, they can plant or replace the dot executable with a malicious script or binary that mimics the expected interface but executes arbitrary commands instead of rendering graphs.

This vulnerability represents a classic insecure external command invocation scenario where the application trusts user-controllable input paths without sufficient validation. The impact is significant for any local low-privileged attacker who has write access to a directory on the victim's PATH, such as /tmp or other world-writable locations often included in default configurations. By exploiting this flaw, an attacker can achieve remote code execution with the privileges of the user running the NLTK application when dot2img is called directly or when DependencyGraph.repr_svg attempts to render a graph. This bypasses previous mitigations implemented for CVE-2026-78680, which addressed similar issues but left this residual writable absolute PATH element vulnerability unpatched until version 3.10.4.

From an industry standards perspective, this flaw aligns with CWE-78 Improper Neutralization of Special Elements used in an OS Command and CWE-22 Path Traversal concepts related to insecure path resolution. In the context of the MITRE ATT&CK framework, this vulnerability facilitates lateral movement or privilege escalation through command injection techniques, specifically leveraging external utility binaries that are commonly pre-installed on systems. The attack vector relies on local file system access rather than network exposure, making it a significant risk in multi-user environments where users share PATH directories or have compromised accounts with write permissions to common temporary folders.

To mitigate this vulnerability, organizations must upgrade NLTK to version 3.10.4 or later immediately upon availability. This update includes the necessary fixes to ensure that external executables are resolved and invoked through secure pathways that enforce strict validation of ownership and writability before execution. Additionally, system administrators should review PATH configurations on affected systems to minimize world-writable directories included in the search path for executable files. Implementing stricter file permission policies and auditing scripts that invoke external commands can further reduce the attack surface associated with insecure command invocation practices in Python-based applications.

Responsible

GitHub M

Reservation

11/12/2026

Disclosure

11/14/2026

Moderation

accepted

CPE

ready

EPSS

0.00184

KEV

no

Activities

very low

Sources

Interested in the pricing of exploits?

See the underground prices here!