CVE-2026-128138

An NLTK Java tool could execute code supplied through untrusted launcher arguments

NLTK project · Natural Language Toolkit · Java NLP tool launcher

First documented disclosure · Review checkpoint

Summary

Applications that passed external command arguments to NLTK’s Java wrapper could expose the application account to unauthorized code execution.

Severity and exploitation evidence

Critical · 9.8/10 · CVSS 3.1. Severity source.

Exploitation not established: The NLTK advisory describes the vulnerability and its preconditions. The reviewed sources identify no malicious use.

Exploitation evidence source

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

The earlier Java launch hardening left a second argument channel able to select an unintended execution mode.

Conditions required

An application passes untrusted input into the command arguments for a Java-backed NLP tool.

Potential impact

Java code could run with the NLP application’s permissions.

Affected versions and configurations

3.10.3

Fix and mitigation status

3.10.4.

Practical next steps

Upgrade to NLTK 3.10.4 or a later fixed release.

Operating lesson

Keep launcher arguments under application control and load model or tool artifacts from trusted locations.

Evidence and limits

The issue-specific patch was public by 2026-08-20. The fixed release shipped October 21. The November 15 maintainer advisory supplies the identifier and affected versions. This is a historical addition.

Sources