SecurityFan score 66 · Tier A
NLTK incomplete fix: additional JVM/JAR sandbox bypass through unvalidated launcher tokens in java() command arguments (CVE-2026-128138)
The Brief
- The GitHub Advisory Database published CVE-2026-128138 on 2026-11-20 for NLTK, described as an incomplete fix.
- The bypass works through unvalidated launcher tokens in java() command arguments, allowing JVM/JAR sandbox escape.
- NLTK 3.10.3 includes hardening aimed at JVM argument-injection and untrusted JAR/classpath execution, but the advisory calls the fix incomplete.
Why it matters
Code that passes untrusted input into nltk.internals.java() may still be exposed to sandbox bypass, even on NLTK 3.10.3.
Who’s affected
- Projects using nltk.internals.java() with untrusted arguments
- Projects running NLTK 3.10.3 that rely on its JVM sandboxing
What to do
- Review every call to nltk.internals.java() and make sure no untrusted input reaches its command arguments.
- Watch the advisory for a complete fix before relying on the JVM sandbox.
- NLTK 3.10.3
- CVE-2026-128138
- #nltk
- #python
- #java
- #sandbox-bypass
- #vulnerability
- #cve
Affects nltk. Summary NLTK 3.10.3 contains security hardening intended to close JVM argument-injection and untrusted JAR/classpath execution paths in nltk.internals.java(), including the issue published as GHSA-m4rf-3fr8-xwx3. The patched options channel correctly rejects Java…