International
The Morning Dev

Only the news worth knowing

‹
 
A66/100

Vulnerability · critical · CVSS 9.8

NLTK incomplete fix leaves JVM sandbox bypass CVE-2026-128138

Tier A · Patch today – Before you go home

Who’s exposed: Applications passing untrusted input to nltk.internals.java()

Tier A because: Core infrastructure or popular tool AND remote, no login AND full takeover

Reach

Attack

Damage

Fix

Popular tool · Public exploit · Remote, no login · Full takeover

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.

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.

The checklist behind the tier

Checklist · 5 of 10 yes
YesHits tech teamsJudgment: NLTK is a Python NLP library that developers build with.
NoCore infrastructureJudgment: NLTK is a single framework, not software nearly every team runs.
YesPopular toolJudgment: NLTK is a widely used, mainstream Python NLP library.
NoExploited in the wildGitHub Advisory Database: describes a vulnerability only; no observed attacks reported.
YesPublic exploitCISA SSVCCISA rates exploitation of CVE-2026-128138 as proof of concept public
YesRemote, no loginCVSSCVE-2026-128138: CVSS 9.8 – network, no privileges, no user interaction
YesFull takeoverCVSSCVE-2026-128138: CVSS rates confidentiality and integrity impact high
NoSecrets exposedGitHub Advisory Database: no data theft or secret exposure reported.
NoSupply chainGitHub Advisory Database: a normal vulnerability in NLTK; no compromised package or malicious code reported.
NoNo fix yetGitHub AdvisoryGitHub Advisory: nltk fixed in 3.10.4

The official record

From CVE.org, CISA’s Known Exploited Vulnerabilities catalog, FIRST EPSS and the GitHub Advisory Database. Where these answer a checklist fact, they win over the reporting.

  • CVE-2026-128138 ↗CVSS 9.8 critical AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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

    Exploited
    Proof of concept public (CISA)
    Fix
    • nltk (pip) fixed in 3.10.4
    Weakness
    CWE-77, CWE-88

    NVDGHSA-x8q7-6c7m-52gw

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

Source

NLTK incomplete fix: additional JVM/JAR sandbox bypass through unvalidated launcher tokens in java() command arguments (CVE-2026-128138) ↗ GitHub Advisory Database · 2h ago

First seen · 1 source · Full story page · How tiers are decided