CVE-2026-128138: nltk · Command Injection
Affects nltkSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical : upgrade to 3.10.4 as a priority.
Data as of 19 Nov 2026, 18:11 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 9.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:HExploitation evidence
Disclosed: evidence found.
CVE published 19 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 18 Nov 2026.
What to do
Upgrade nltk to 3.10.4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| nltknltk | Affected
| Fixed in
|
AI-suggested
Upgrade NLTK to version 3.10.4 or later, where this vulnerability is fixed. No other mitigations are indicated by the vendor advisory. Users running affected versions should apply the official patch promptly.
Description
A command injection vulnerability (CWE-77) exists in NLTK versions 3.10.3 up to but not including 3.10.4. The issue arises because the Java launcher token validation in the JVM hardening feature does not require the first token of the caller-controlled command sequence to be a main class. This allows an attacker to supply '-jar' or an '@argfile' through certain NLTK components, leading to execution of arbitrary Java bytecode. The vulnerability is fixed in version 3.10.4.