WhatBrokeToday
GTA 6FAQ
PyPI

NLTK JVM/JAR Sandbox Bypass Vulnerability via Unvalidated Launcher Tokens

critical

Is it fixed? Not yet.

Ongoing since Nov 19, 23:55 UTC. First reported Nov 19, 23:55 UTC.

What happened

NLTK versions 3.10.3 contain an incomplete fix allowing an additional JVM/JAR sandbox bypass through unvalidated launcher tokens in java() command arguments (CVE-2026-128138). The vulnerability has been addressed in NLTK version 3.10.4.

What caused it?

An additional JVM/JAR sandbox bypass through unvalidated launcher tokens in java() command arguments.

Source: github.com

No verified workaround yet

None of the linked reports describe a mitigation. This page updates when one appears.

Official fix

Timeline

  1. Investigating(current)
  2. Workaround available(upcoming)
  3. Resolved(upcoming)
  1. First report on security advisory

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

    Source

Evidence

1 report · 1 CVEShow
  1. [1]
    CVE First report
    NLTK incomplete fix: additional JVM/JAR sandbox bypass through unvalidated launcher tokens in java() command arguments(opens security advisory in a new tab)

    Fixed in: nltk 3.10.4. Critical severity (CVE-2026-128138). Affected: nltk (pip) >= 3.10.3, < 3.10.4. ## 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 argument-file references such as `@/path/to/args` and launcher modes such as `-jar`. However, an additional argument channel…

    by GitHub Advisory Database 0upvotes 0comments

FAQ

What happened in the PyPI issue?

NLTK versions 3.10.3 contain an incomplete fix allowing an additional JVM/JAR sandbox bypass through unvalidated launcher tokens in java() command arguments (CVE-2026-128138). The vulnerability has been addressed in NLTK version 3.10.4.

What is affected by the PyPI issue?

PyPI (versions: >= 3.10.3, < 3.10.4).

When did the PyPI issue start and end?

It started Nov 19, 23:55 UTC and is still ongoing (1 h 3 min so far). This page updates as it develops.

How do I get alerts for PyPI?

Subscribe to the PyPI RSS feed for every new PyPI incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether PyPI is down. PyPI feed

Where does this information come from?

WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 1 report from 1 independent source.