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

Published Nov 19, 2026
·
Updated

NLTK (Natural Language Toolkit) is a suite of open source Python modules, data sets, and tutorials supporting research and development in Natural Language Processing. From 3.10.3 until 3.10.4, the NLTK 3.10.3 JVM hardening validates Java launcher tokens in the options channel but appends the caller-controlled cmd sequence without requiring its first token to be a main class. Supplying -jar or an @argfile through nltk.internals.java or StanfordSegmenter.javaclass can therefore execute attacker-selected Java bytecode without the unsafe-JAR opt-in. This issue is fixed in version 3.10.4.

Affected Software

1 affected component
pypi/nltk>=3.10.3<3.10.4

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 3.10.4

Event History

Nov 19, 2026
CVE Published
via MITRE·05:53 PM
Data Sourced
via MITRE·05:53 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:18 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed?

Deployments using NLTK from version 3.10.3 up to, but not including, 3.10.4 are affected when they invoke Java through nltk.internals.java or StanfordSegmenter.java_class with caller-controlled command arguments.

2

What does an attacker need to exploit this issue?

An attacker needs control over the cmd sequence passed to the affected Java invocation paths. They can supply -jar or an @argfile as the first command token to run attacker-selected Java bytecode without enabling the unsafe-JAR opt-in.

3

Is the JVM hardening in 3.10.3 sufficient protection?

No. Version 3.10.3 validates launcher tokens in the options channel, but does not require the first caller-controlled cmd token to be a main class.

4

What is the remediation?

Upgrade NLTK to version 3.10.4, which fixes the issue. Until upgrading, avoid passing caller-controlled cmd sequences to nltk.internals.java or StanfordSegmenter.java_class, particularly values that could begin with -jar or @argfile.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203