NLTK before 3.10.3 fails to validate JVM options passed through the per-call options parameter in the java() function, allowing attackers to inject dangerous JVM flags. Attackers can supply malicious options like -agentpath, -javaagent, or @argfile to Stanford wrapper classes to achieve arbitrary code execution.
Advisories
No advisories yet.
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
Tue, 25 Aug 2026 15:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | NLTK before 3.10.3 fails to validate JVM options passed through the per-call options parameter in the java() function, allowing attackers to inject dangerous JVM flags. Attackers can supply malicious options like -agentpath, -javaagent, or @argfile to Stanford wrapper classes to achieve arbitrary code execution. | |
| Title | NLTK before 3.10.3 JVM Argument Injection via Per-Call Options | |
| First Time appeared |
Nltk
Nltk nltk |
|
| Weaknesses | CWE-88 | |
| CPEs | cpe:2.3:a:nltk:nltk:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Nltk
Nltk nltk |
|
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: VulnCheck
Published:
Updated: 2026-08-25T15:16:00.949Z
Reserved: 2026-08-25T11:10:13.698Z
Link: CVE-2026-79675
No data.
Status : Received
Published: 2026-08-25T16:17:28.013
Modified: 2026-08-25T16:17:28.013
Link: CVE-2026-79675
No data.
OpenCVE Enrichment
Updated: 2026-08-25T19:00:07Z
Weaknesses