CVE-2026-79675

NLTK before 3.10.3 JVM Argument Injection via Per-Call Options

Published Aug 25, 2026 CVSS 4.0 · 9.3 Critical EPSS < 1% KEV · Not listed
Description
NLTK before 3.10.3 fails to validate JVM options passed through the per-call options parameter in the java() function, allowing attackers to inject dangerous JVM flags. Attackers can supply malicious options like -agentpath, -javaagent, or @argfile to Stanford wrapper classes to achieve arbitrary code execution.

Analysis

AI-generated

Technical impact

The flaw in NLTK prior to version 3.10.3 permits an attacker to pass unvalidated JVM options to the per‑call options parameter in the java() function, which the underlying Stanford wrapper classes use. By injecting options such as -agentpath, -javaagent, or @argfile, an attacker can cause the JVM to load malicious agents or execute arbitrary code. The weakness is a classic command injection style vulnerability classified under CWE‑88.

Affected Systems

The affected product is the NLTK library (nltk). All releases before version 3.10.3 are vulnerable; the issue was addressed in 3.10.3 and later.

Risk and Exploitability

The CVSS score of 9.3 places this vulnerability in the critical range, indicating a high potential for impact. The EPSS score is not available, but the lack of a KEV listing suggests the vulnerability is not yet widely exploited. The likely attack vector is local or any scenario where an attacker can run Python code that invokes nltk's java() function with malicious options. If unmitigated, an attacker could achieve arbitrary code execution on the affected host.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to NLTK v3.10.3 or later
  • If an upgrade is not immediately possible, implement input validation to reject any JVM option that is not explicitly allowed
  • Avoid exposing the java() function to untrusted input or restrict its usage to trusted code execution paths

Generated by OpenCVE AI on August 25, 2026 at 17:03 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-m4rf-3fr8-xwx3 NLTK: JVM argument injection bypass via per-call options in the NLTK Stanford wrappers (incomplete fix of CVE-2026-12841)
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description NLTK before 3.10.3 fails to validate JVM options passed through the per-call options parameter in the java() function, allowing attackers to inject dangerous JVM flags. Attackers can supply malicious options like -agentpath, -javaagent, or @argfile to Stanford wrapper classes to achieve arbitrary code execution.
Title NLTK before 3.10.3 JVM Argument Injection via Per-Call Options
First Time appeared Nltk
Nltk nltk
Weaknesses CWE-88
CPEs cpe:2.3:a:nltk:nltk:*:*:*:*:*:*:*:*
Vendors & Products Nltk
Nltk nltk
References
Metrics cvssV3_1

{'score': 9.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}

cvssV4_0

{'score': 9.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-88

    Improper Neutralization of Argument Delimiters in a Command ('Argument Injection')

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Aug 27, 2026, 4:24 PM
Reserved
Aug 25, 2026, 11:10 AM
Status
Analyzed
Published
Aug 25, 2026, 4:17 PM
Modified
Sep 1, 2026, 8:08 PM
Severity
Important
Public date
Aug 25, 2026, 3:16 PM