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.
References
| Link | Resource |
|---|---|
| https://github.com/nltk/nltk/security/advisories/GHSA-m4rf-3fr8-xwx3 | Exploit Mitigation Vendor Advisory |
| https://www.vulncheck.com/advisories/nltk-before-jvm-argument-injection-via-per-call-options | Third Party Advisory |
Configurations
History
No history.
Information
Published : 2026-08-25 16:17
Updated : 2026-09-01 20:08
NVD link : CVE-2026-79675
Mitre link : CVE-2026-79675
CVE.ORG link : CVE-2026-79675
JSON object : View
Products Affected
nltk
- nltk
CWE
CWE-88
Improper Neutralization of Argument Delimiters in a Command ('Argument Injection')
