CVE-2026-79675: NLTK JVM Argument Injection Bypass Vulnerability

CRITICAL
Advisory Identifier: GHSA-m4rf-3fr8-xwx3
CVSS 9.8
CWE-88
Published
Advisory Summary

CVE-2026-79675 is a CRITICAL (CVSS 9.8) jvm argument injection bypass vulnerability (CWE-88: Improper Neutralization of Argument Delimiters in a Command ('Argument Injection')) affecting NLTK libraries in the PyPI ecosystem. The issue involves jvm argument injection bypass via per-call options in the nltk stanford wrappers (incomplete fix of cve-2026-12841). Remediation is available by upgrading affected packages to version 3.10.3.

CVE-2026-79675 at a Glance

CVE Identifier CVE-2026-79675
GHSA Identifier GHSA-m4rf-3fr8-xwx3
Severity CRITICAL
CVSS v3.1 Base Score 9.8
CWE Classification CWE-88: Improper Neutralization of Argument Delimiters in a Command ('Argument Injection')
Affected Product NLTK
Package Ecosystem PyPI
Published Date
Last Updated

Security Impact

CVSS: 9.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2026-79675

To remediate this vulnerability, upgrade all affected NLTK dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

nltk fixed: 3.10.3
pip install nltk>=3.10.3
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

pip show nltk

How to Check if You Are Affected

To determine whether your Python environment is affected by CVE-2026-79675, inspect your installed packages using pip:

pip show nltk

Analyze the terminal output to locate any version of NLTK in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.10.3), your application is affected.

Note: The pip show nltk command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-88: Improper Neutralization of Argument Delimiters in a Command ('Argument Injection'), where the product constructs a string for a command to be executed by a separate component in another control sphere, but it does not properly delimit the intended arguments, options, or switches within that command string. In NLTK, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Vulnerability The fix for CVE-2026-12841 (CWE-88, JVM argument injection) added `_validate_java_options()` to block dangerous JVM flags such as `-agentlib`, `-agentpath`, `-javaagent`, `-Xrunjdwp`, and `@argfile` references. However, the validation is only applied when setting global options via `config_java()`. The `java()` function's per-call `options` parameter -- added by PR #3683 (CVE-2026-12615 fix) -- passes options directly to `subprocess.Popen` without calling `_validate_java_options()`. All four Stanford Java wrapper classes accept user-supplied `java_options` and route them through the unvalidated per-call path, bypassing the CVE-2026-12841 fix entirely. ## Root Cause In `nltk/internals.py`, the `java()` function (line 128) accepts an `options` keyword argument. When `options` is not None, it is converted to a list and prepended to the JVM command (lines 211-217) without any validation: ```python # nltk/internals.py, lines 211-217 (HEAD) if options is None: java_options = _java_options # validated by config_java() else: if isinstance(options, str): options = options.split() java_options = list(options) # NO validation cmd = [_java_bin] + java_options + cmd ``` Compare with `config_java()` (line 92) which does validate: ```python # nltk/internals.py, lines 122-123 _validate_java_options(options) _java_options[:] = options ``` The four affected wrapper classes store user-supplied `java_options` without validation and pass them through the unvalidated per-call path: 1. `GenericStanfordParser` (`nltk/parse/stanford.py`): constructor parameter at line 39, stored at line 78, passed at lines 247 and 256 2. `StanfordTagger` (`nltk/tag/stanford.py`): constructor parameter at line 51, stored at line 79, passed at line 118 3. `StanfordTokenizer` (`nltk/tokenize/stanford.py`): constructor parameter at line 43, stored at line 66, passed at line 109 4. `StanfordSegmenter` (`nltk/tokenize/stanford_segmenter.py`): constructor parameter at line 68, stored at line 117, passed at line 337 ## Proof of Concept ```python from nltk.internals import config_java, java, _validate_java_options # 1. The global config_java() path correctly blocks dangerous flags: try: config_java(options=["-agentpath:/tmp/evil.so"]) except ValueError as e: print(f"config_java blocked: {e}") # blocked as expected # 2. The per-call options path does NOT block them: # (Would execute if Java were installed) # java(["SomeClass"], classpath=".", options=["-agentpath:/tmp/evil.so"]) # This passes "-agentpath:/tmp/evil.so" directly to subprocess.Popen # 3. Stanford wrapper classes pass through without validation: # from nltk.parse.stanford import StanfordParser # parser = StanfordParser(java_options="-agentpath:/tmp/evil.so") # parser.parse(...) # dangerous flag reaches JVM # Verify the gap directly: dangerous_opts = ["-agentpath:/tmp/evil.so"] try: _validate_java_options(dangerous_opts) print("Would have been caught") except ValueError: print("Correctly rejected by _validate_java_options()") # But java() itself never calls _validate_java_options(): import inspect source = inspect.getsource(java) assert "_validate_java_options" not in source, "java() does not validate options" print("Confirmed: java() does not call _validate_java_options()") ``` ## Impact An attacker who controls the `java_options` parameter to any NLTK Stanford wrapper class can inject arbitrary JVM flags, including: - `-agentpath:/path/to/malicious.so` -- loads a native agent, achieving arbitrary code execution - `-javaagent:/path/to/malicious.jar` -- loads a Java agent for bytecode manipulation - `-agentlib:jdwp=transport=dt_socket,server=y,address=*:5005` -- enables remote debugging, allowing remote code execution - `@/path/to/argfile` -- expands an argument file, which can smuggle any of the above This is exploitable in scenarios where NLTK is deployed as a service and `java_options` is derived from user input, configuration files, or environment variables. The PR #3647 commit message explicitly states the fix was intended to cover "StanfordSegmenter, and GenericStanfordParser" but the implementation only validates in `config_java()`. ## Suggested Fix Add `_validate_java_options()` to the `java()` function's per-call options handling: ```python # nltk/internals.py, in the java() function if options is None: java_options = _java_options else: if isinstance(options, str): options = options.split() java_options = list(options) _validate_java_options(java_options) # ADD THIS LINE cmd = [_java_bin] + java_options + cmd ``` This single-line addition closes the bypass for all four Stanford wrapper classes and any future callers of `java(options=...)`. ### AI tooling AI assistance was used for the code audit and for drafting this report. The finding were manually verified against the project's source at the location cited above before reporting it, and the severity and impact assessment are the reporters.

CVE-2026-79675 Affected NLTK Versions

1 component(s)
Fixed Versions:
3.10.3
Product / Package Ecosystem Affected Versions Fixed Version
nltk
PyPI
< 3.10.3
3.10.3

References

Frequently Asked Questions

What is CVE-2026-79675?
CVE-2026-79675 is a security vulnerability in NLTK involving JVM argument injection bypass via per-call options in the NLTK Stanford wrappers (incomplete fix of CVE-2026-12841) under CWE-88: Improper Neutralization of Argument Delimiters in a Command ('Argument Injection').
Which NLTK versions are affected?
Affected versions include releases prior to 3.10.3 across affected packages: nltk.
What version fixes CVE-2026-79675?
Upgrading to 3.10.3 (or the latest patched release for your respective branch) resolves the vulnerability.
Is nltk affected?
Yes, nltk is affected in releases prior to 3.10.3. Upgrade your dependency to 3.10.3 or later.
What is the CVSS score of CVE-2026-79675?
CVE-2026-79675 has a CVSS v3.1 base score of 9.8 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-79675?
CVE-2026-79675 is classified under CWE-88: Improper Neutralization of Argument Delimiters in a Command ('Argument Injection') (The product constructs a string for a command to be executed by a separate component in another control sphere, but it does not properly delimit the intended arguments, options, or switches within that command string.).
How can I check PyPI dependencies for CVE-2026-79675?
Run the dependency tree command: 'pip show nltk'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-m4rf-3fr8-xwx3",
  "modified" : "2026-09-01T20:38:22Z",
  "published" : "2026-09-01T20:38:22Z",
  "aliases" : [ "CVE-2026-79675" ],
  "summary" : "NLTK: JVM argument injection bypass via per-call options in the NLTK Stanford wrappers (incomplete fix of CVE-2026-12841)",
  "details" : "## Vulnerability\n\nThe fix for CVE-2026-12841 (CWE-88, JVM argument injection) added `_validate_java_options()` to block dangerous JVM flags such as `-agentlib`, `-agentpath`, `-javaagent`, `-Xrunjdwp`, and `@argfile` references. However, the validation is only applied when setting global options via `config_java()`. The `java()` function's per-call `options` parameter -- added by PR #3683 (CVE-2026-12615 fix) -- passes options directly to `subprocess.Popen` without calling `_validate_java_options()`.\n\nAll four Stanford Java wrapper classes accept user-supplied `java_options` and route them through the unvalidated per-call path, bypassing the CVE-2026-12841 fix entirely.\n\n## Root Cause\n\nIn `nltk/internals.py`, the `java()` function (line 128) accepts an `options` keyword argument. When `options` is not None, it is converted to a list and prepended to the JVM command (lines 211-217) without any validation:\n\n```python\n# nltk/internals.py, lines 211-217 (HEAD)\nif options is None:\n    java_options = _java_options       # validated by config_java()\nelse:\n    if isinstance(options, str):\n        options = options.split()\n    java_options = list(options)       # NO validation\ncmd = [_java_bin] + java_options + cmd\n```\n\nCompare with `config_java()` (line 92) which does validate:\n\n```python\n# nltk/internals.py, lines 122-123\n_validate_java_options(options)\n_java_options[:] = options\n```\n\nThe four affected wrapper classes store user-supplied `java_options` without validation and pass them through the unvalidated per-call path:\n\n1. `GenericStanfordParser` (`nltk/parse/stanford.py`): constructor parameter at line 39, stored at line 78, passed at lines 247 and 256\n2. `StanfordTagger` (`nltk/tag/stanford.py`): constructor parameter at line 51, stored at line 79, passed at line 118\n3. `StanfordTokenizer` (`nltk/tokenize/stanford.py`): constructor parameter at line 43, stored at line 66, passed at line 109\n4. `StanfordSegmenter` (`nltk/tokenize/stanford_segmenter.py`): constructor parameter at line 68, stored at line 117, passed at line 337\n\n## Proof of Concept\n\n```python\nfrom nltk.internals import config_java, java, _validate_java_options\n\n# 1. The global config_java() path correctly blocks dangerous flags:\ntry:\n    config_java(options=[\"-agentpath:/tmp/evil.so\"])\nexcept ValueError as e:\n    print(f\"config_java blocked: {e}\")   # blocked as expected\n\n# 2. The per-call options path does NOT block them:\n# (Would execute if Java were installed)\n# java([\"SomeClass\"], classpath=\".\", options=[\"-agentpath:/tmp/evil.so\"])\n# This passes \"-agentpath:/tmp/evil.so\" directly to subprocess.Popen\n\n# 3. Stanford wrapper classes pass through without validation:\n# from nltk.parse.stanford import StanfordParser\n# parser = StanfordParser(java_options=\"-agentpath:/tmp/evil.so\")\n# parser.parse(...)  # dangerous flag reaches JVM\n\n# Verify the gap directly:\ndangerous_opts = [\"-agentpath:/tmp/evil.so\"]\ntry:\n    _validate_java_options(dangerous_opts)\n    print(\"Would have been caught\")\nexcept ValueError:\n    print(\"Correctly rejected by _validate_java_options()\")\n\n# But java() itself never calls _validate_java_options():\nimport inspect\nsource = inspect.getsource(java)\nassert \"_validate_java_options\" not in source, \"java() does not validate options\"\nprint(\"Confirmed: java() does not call _validate_java_options()\")\n```\n\n## Impact\n\nAn attacker who controls the `java_options` parameter to any NLTK Stanford wrapper class can inject arbitrary JVM flags, including:\n\n- `-agentpath:/path/to/malicious.so` -- loads a native agent, achieving arbitrary code execution\n- `-javaagent:/path/to/malicious.jar` -- loads a Java agent for bytecode manipulation\n- `-agentlib:jdwp=transport=dt_socket,server=y,address=*:5005` -- enables remote debugging, allowing remote code execution\n- `@/path/to/argfile` -- expands an argument file, which can smuggle any of the above\n\nThis is exploitable in scenarios where NLTK is deployed as a service and `java_options` is derived from user input, configuration files, or environment variables. The PR #3647 commit message explicitly states the fix was intended to cover \"StanfordSegmenter, and GenericStanfordParser\" but the implementation only validates in `config_java()`.\n\n## Suggested Fix\n\nAdd `_validate_java_options()` to the `java()` function's per-call options handling:\n\n```python\n# nltk/internals.py, in the java() function\nif options is None:\n    java_options = _java_options\nelse:\n    if isinstance(options, str):\n        options = options.split()\n    java_options = list(options)\n    _validate_java_options(java_options)   # ADD THIS LINE\ncmd = [_java_bin] + java_options + cmd\n```\n\nThis single-line addition closes the bypass for all four Stanford wrapper classes and any future callers of `java(options=...)`.\n\n### AI tooling\n\nAI assistance was used for the code audit and for drafting this report. The finding were manually verified against the project's source at the location cited above before reporting it, and the severity and impact assessment are the reporters.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
  }, {
    "type" : "CVSS_V4",
    "score" : "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "nltk"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "3.10.3"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 3.10.2"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/nltk/nltk/security/advisories/GHSA-m4rf-3fr8-xwx3"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-79675"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/nltk/nltk/commit/8fa9650b6009aacfdebbc33d2a08d32c0858ea6c"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/nltk/nltk"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/nltk/nltk/releases/tag/v3.10.3"
  }, {
    "type" : "WEB",
    "url" : "https://www.vulncheck.com/advisories/nltk-before-jvm-argument-injection-via-per-call-options"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-88" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-09-01T20:38:22Z",
    "nvd_published_at" : null
  }
}