Arbitrary code execution via unverified Stanford JARs
Published Jul 4, 2026 · Updated Jul 4, 2026
Code injection in NLTK 3.9.3 and earlier allows local users to execute arbitrary code through a supplied Stanford JAR file. Five Stanford interface classes pass user-controlled JAR paths to java(), which invokes subprocess.Popen() without verifying integrity. Execution requires an application or user to select or replace a JAR path; the bytecode runs with the Python process's privileges.
Summary
What happened
Code injection in NLTK 3.9.3 and earlier allows local users to execute arbitrary code through a supplied Stanford JAR file. Five Stanford interface classes pass user-controlled JAR paths to java(), which invokes subprocess.Popen() without verifying integrity. Execution requires an application or user to select or replace a JAR path; the bytecode runs with the Python process's privileges.
The record
- CVE
- CVE-2026-12252
- Published
- Jul 4, 2026
- Updated
- Jul 4, 2026
- Vendor
- NLTK Project
- Product
- NLTK
- Classifications
- CWE-94, CWE-347, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 4, 2026CVE publishedPublication date reported by the CVE source.
- Jul 4, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <=latest
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Huntr untrusted Stanford JAR execution proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo