Skip to main content
CVE-2026-128138VulnerabilityPublished

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

Affects nltkSource GCVE Database

0
Compare
Authoritative record:CVE-2026-128138· Critical 9.8

Not known to be exploited · CVSS 9.8 Critical : upgrade to 3.10.4 as a priority.

Data as of 20 Nov 2026, 01:50 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.19.8
Patch
Available – fixed in 3.10.4
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade nltk to 3.10.4.

Affected software

ProductAffectedFixed in
PyPInltkAffected
  • >=3.10.3 <3.10.4
Fixed in
  • 3.10.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade to NLTK version 3.10.4 or later, where this incomplete fix is addressed. The vendor advisory confirms that the issue is fixed in 3.10.4. No other mitigations are required once the patch is applied.

Description

NLTK version 3.10.3 contains an incomplete fix for JVM argument injection and untrusted JAR execution vulnerabilities in the nltk.internals.java() function. While the patch blocks unsafe launcher tokens in the 'options' argument, it fails to validate the first item of the 'cmd' argument sequence, allowing an attacker to supply launcher tokens such as '-jar' or '@argfile' to execute arbitrary external JAR files. This bypass affects both direct calls to nltk.internals.java() and the higher-level StanfordSegmenter interface. The issue is fixed in version 3.10.4.

References

Community reviews

Loading reviews…