CVE-2026-129234
Awaiting Analysis Awaiting Analysis - Queue

Privilege Escalation in NLTK via Prover9 Binary Path Injection

Vulnerability report for CVE-2026-129234, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-19

Last updated on: 2026-11-19

Assigner: GitHub, Inc.

Description

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, Prover9Parent.config_prover9 and Mace accept a relative binary_location and pass it to find_binary as path_to_bin, disabling the bare-name absolute-path guard. A local attacker who can plant prover9 or mace4 in the resolved working directory can cause subprocess.Popen to execute that binary with the invoking user's privileges. This issue is fixed in version 3.10.4.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-19
Last Modified
2026-11-19
Generated
2026-11-20
AI Q&A
2026-11-20
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
nltk nltk 3.10.4

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-426 The product searches for critical resources using an externally-supplied search path that can point to resources that are not under the product's direct control.
CWE-427 The product uses a fixed or controlled search path to find resources, but one or more locations in that path can be under the control of unintended actors.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in NLTK (CVE-2026-129234) involves untrusted search paths in binary execution. Prior to version 3.10.4, components like Prover9Parent.config_prover9 and Mace accepted relative paths for binary locations. These paths were passed to subprocess.Popen without validation, allowing attackers to place malicious binaries in directories that could be resolved to the current working directory. When executed, these binaries would run with the user's privileges, enabling arbitrary code execution.

Detection Guidance

Check NLTK version with pip show nltk. If version is below 3.10.4, the system is vulnerable. Inspect Python scripts using NLTK's Prover9Parent.config_prover9 or Mace for relative path usage in binary_location configurations.

Impact Analysis

If you use NLTK versions before 3.10.4, an attacker with local access could exploit this to run malicious code on your system. The attacker would need to place a decoy binary in a directory you access, such as your working directory. When NLTK attempts to execute the binary, it would run the attacker's code instead, potentially stealing data, installing malware, or performing other unauthorized actions with your user permissions.

Compliance Impact

This vulnerability could lead to unauthorized code execution, potentially causing data breaches or unauthorized access to sensitive information. For GDPR, this may violate principles of data protection and security. For HIPAA, it could compromise protected health information. Organizations using affected NLTK versions may face compliance violations, legal liabilities, and reputational damage if exploited.

Mitigation Strategies

Upgrade NLTK to version 3.10.4 or later using pip install --upgrade nltk. Review and update any configurations using relative paths for binary_location to use absolute paths only.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-129234. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...