International
The Morning Dev

Only the news worth knowing

‹
 

SecurityFan score 66 · Tier A

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

GitHub Advisory Database ·

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

  1. Review every call to nltk.internals.java() and make sure no untrusted input reaches its command arguments.
  2. Watch the advisory for a complete fix before relying on the JVM sandbox.

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…

Timeline

  1. GitHub Advisory Database

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

  2. Advisory published: NLTK incomplete fix leaves JVM/JAR sandbox bypass

How do you feel about this?

0 Comments

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