UNKNOWNPyPI →
NLTK before 3.10.3 fails to validate JVM options passed through the per-call options parameter in the java() function, a
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.
Affected packages
- nltk— before 3.10.3
Exploit signal
- Known exploited (CISA KEV)
- No
- EPSS score
- —
- EPSS percentile
- —
EPSS is the probability a CVE is exploited in the wild; percentile is its rank among all CVEs.
Sources
- https://www.vulncheck.com/advisories/nltk-before-jvm-argument-injection-via-per-call-options
- https://github.com/nltk/nltk/security/advisories/GHSA-m4rf-3fr8-xwx3
Structured record: https://osv.dev/vulnerability/PYSEC-2026-3749
Recommended response stack
Snyk — Scan your dependencies in CI and fix this vulnerability.→Socket — Detect malicious and compromised packages before they ship.→
Some links are affiliate links — HackTribune may earn a commission at no extra cost to you.
Get incidents like this as alerts for your stack.
Join the beta