Security readout for executives and security teams
Plain-English summary
Applications using vulnerable NLTK versions may let untrusted input alter how Java starts. If an application passes attacker-controlled per-call options into affected Stanford wrappers, an attacker could run code with the application's privileges, risking data theft, service disruption, and system compromise.
Executive priority
Prioritize emergency assessment and rapid remediation for internet-facing or multi-tenant systems with reachable affected call paths. Other installations still require prompt version inventory and upgrade planning because successful exploitation could fully compromise the application environment.
Technical view
NLTK versions before 3.10.3 do not validate per-call JVM options passed through java(). Dangerous JVM arguments can reach Stanford wrapper classes, creating CWE-88 argument injection and potential arbitrary code execution. Practical reachability depends on whether an application exposes or derives these options from untrusted input.
Likely exposure
Exposure is most likely in services running NLTK before 3.10.3 that invoke Java-backed Stanford wrappers and permit external input to influence per-call options. Merely installing NLTK does not establish exploitability; vulnerable call paths and attacker-controlled data flow must both be confirmed.
Exploitation context
The supplied CVSS rating is 9.8, reflecting potentially remote, unauthenticated code execution with low complexity. However, the bundle does not report CISA KEV inclusion or provide evidence of active exploitation. Treat the impact as critical while distinguishing theoretical reachability from observed attacks.
Researcher notes
The central validation question is data-flow reachability: can an untrusted source control the per-call options reaching java() through a Stanford wrapper? The sources identify dangerous JVM flag classes but do not establish which applications expose them, how commonly the path is reachable, or whether exploitation has occurred publicly.
Mitigation direction
- Upgrade NLTK to version 3.10.3 or later.
- Prevent untrusted data from controlling java() per-call options.
- Restrict or disable affected Stanford wrapper functionality until upgrading.
- Review vendor guidance for any additional hardening recommendations.
Validation and detection
- Inventory deployed NLTK versions, including transitive and packaged copies.
- Identify uses of java() and Java-backed Stanford wrapper classes.
- Trace whether requests, files, jobs, or messages influence per-call options.
- Confirm production artifacts contain NLTK 3.10.3 or later.
- Review logs and telemetry for unexpected JVM option usage or child-process behavior.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-88: Command execution behavior lookup
Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-79675 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9VulnCheckCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
9.3CriticalVector: 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
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- GitHub Security Advisory (GHSA-m4rf-3fr8-xwx3)CVE reference, VulnCheck · vendor-advisory
- VulnCheck Advisory: NLTK before 3.10.3 JVM Argument Injection via Per-Call OptionsCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Argument Delimiters in a Command
Improper Neutralization of Argument Delimiters in a Command represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.