# NLTK incomplete fix: additional JVM/JAR sandbox bypass through unvalidated launcher tokens in java() command arguments (CVE-2026-128138)

Source: [GitHub Advisory Database](https://github.com/advisories/GHSA-x8q7-6c7m-52gw) · 2026-11-19 · Security
Page: https://themorning.dev/story/nltk-incomplete-fix-additional-jvm-jar-sandbox-bypass-through-unvalidated-launch-83bb05e584052009
Kind: security · Impact: medium

## In 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.

## 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.

## Versions

- NLTK 3.10.3

## CVEs

- CVE-2026-128138

## Timeline

- 2026-11-20: Advisory published: NLTK incomplete fix leaves JVM/JAR sandbox bypass

## Coverage

- [NLTK incomplete fix: additional JVM/JAR sandbox bypass through unvalidated launcher tokens in java() command arguments (CVE-2026-128138)](https://github.com/advisories/GHSA-x8q7-6c7m-52gw) — GitHub Advisory Database, 2026-11-19

Tags: nltk, python, java, sandbox-bypass, vulnerability, cve

---

Brief generated by AI (claude-haiku-5-5) from the reporting listed under Coverage. Headlines belong to their publishers. The Morning Dev – https://themorning.dev
