CVE-2026-79675

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-25. A secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated
9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
75
EG Risk 75/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.8%
EPSS %ILE
54th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 25, 2026

Last Modified

September 1, 2026

Advisory Details (2)

Auto-updated Oct 7, 2026
Patch available. Sources: github.
Web page

NLTK before 3.10.3 JVM Argument Injection via Per-Call Options | Advisories | VulnCheck

https://www.vulncheck.com/advisories/nltk-before-jvm-argument-injection-via-per-call-options
GitHub advisoryMentions a patch (unverified)

JVM argument injection bypass via per-call options in the NLTK Stanford wrappers (incomplete fix of CVE-2026-12841) · Advisory · nltk/nltk · GitHub

https://github.com/nltk/nltk/security/advisories/GHSA-m4rf-3fr8-xwx3

Vendor Advisories for CVE-2026-79675(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-llama-stack-core-rhel9:17891212862026-09-30redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
nltk3.10.0-1 ... 3.9.3-1 (9 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
nltk3.10.0-1 ... 3.9.3-1 (6 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
nltk3.10.0-1, 3.10.1-1, 3.9.1-2, 3.9.2-1, 3.9.3-1
  • every version up to 3.10.3-1: fixed in 3.10.3-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
nltk0.8 ... 3.9b1 (68 versions)
  • every version up to 3.10.3: fixed in 3.10.3
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 26× in last 7d / 103× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 193 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 93 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-14 01:38 UTCEG score recompute
  2. 2026-10-14 01:38 UTCVendor advisory
  3. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  4. 2026-10-12 21:47 UTCEG score recompute
  5. 2026-10-12 21:47 UTCVendor advisory
  6. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  7. 2026-10-12 14:58 UTCEG score recompute
  8. 2026-10-12 05:23 UTCVendor advisory
  9. 2026-10-11 19:22 UTCEG score recompute
  10. 2026-10-11 16:38 UTCEG score recompute
  11. 2026-10-11 13:56 UTCEG score recompute
  12. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  13. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  14. 2026-10-10 16:07 UTCVendor advisory
  15. 2026-10-10 12:02 UTCEG score recompute
  16. 2026-10-10 12:02 UTCVendor advisory
  17. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  18. 2026-10-09 08:03 UTCVendor advisory
  19. 2026-10-09 04:23 UTCEG score recompute
  20. 2026-10-09 04:23 UTCVendor advisory
  21. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  22. 2026-10-08 07:02 UTCVendor advisory
  23. 2026-10-08 03:17 UTCEG score recompute
  24. 2026-10-08 03:17 UTCVendor advisory
  25. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.8% · 54th percentile
Show 75 more
  1. 2026-10-07 10:29 UTCVendor advisory
  2. 2026-10-07 06:49 UTCVendor advisory
  3. 2026-10-07 03:09 UTCVendor advisory
  4. 2026-10-06 23:28 UTCVendor advisory
  5. 2026-10-06 19:48 UTCVendor advisory
  6. 2026-10-06 16:09 UTCEG score recompute
  7. 2026-10-06 16:09 UTCVendor advisory
  8. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  9. 2026-10-06 11:25 UTCVendor advisory
  10. 2026-10-06 07:43 UTCVendor advisory
  11. 2026-10-06 02:33 UTCVendor advisory
  12. 2026-10-05 20:41 UTCEG score recompute
  13. 2026-10-05 20:41 UTCVendor advisory
  14. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  15. 2026-10-05 17:01 UTCVendor advisory
  16. 2026-10-05 11:21 UTCVendor advisory
  17. 2026-10-05 07:38 UTCVendor advisory
  18. 2026-10-05 03:58 UTCVendor advisory
  19. 2026-10-04 23:31 UTCVendor advisory
  20. 2026-10-04 19:50 UTCVendor advisory
  21. 2026-10-04 13:23 UTCVendor advisory
  22. 2026-10-04 09:34 UTCVendor advisory
  23. 2026-10-04 05:53 UTCVendor advisory
  24. 2026-10-04 02:13 UTCVendor advisory
  25. 2026-10-03 20:14 UTCVendor advisory
  26. 2026-10-03 16:26 UTCEG score recompute
  27. 2026-10-03 16:26 UTCVendor advisory
  28. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  29. 2026-10-03 05:02 UTCVendor advisory
  30. 2026-10-03 01:13 UTCVendor advisory
  31. 2026-10-02 21:33 UTCEG score recompute
  32. 2026-10-02 21:33 UTCVendor advisory
  33. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  34. 2026-10-02 17:44 UTCVendor advisory
  35. 2026-10-02 14:03 UTCVendor advisory
  36. 2026-10-02 10:08 UTCVendor advisory
  37. 2026-10-02 06:28 UTCVendor advisory
  38. 2026-10-02 01:18 UTCVendor advisory
  39. 2026-10-01 20:05 UTCEG score recompute
  40. 2026-10-01 20:05 UTCVendor advisory
  41. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  42. 2026-10-01 12:56 UTCVendor advisory
  43. 2026-10-01 09:16 UTCVendor advisory
  44. 2026-10-01 05:36 UTCVendor advisory
  45. 2026-10-01 01:08 UTCVendor advisory
  46. 2026-09-30 20:15 UTCEG score recompute
  47. 2026-09-30 06:47 UTCEG score recompute
  48. 2026-09-29 15:24 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  49. 2026-09-29 01:35 UTCEG score recompute
  50. 2026-09-28 15:15 UTCEG score recompute
  51. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  52. 2026-09-27 17:00 UTCEG score recompute
  53. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  54. 2026-09-26 22:05 UTCEG score recompute
  55. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  56. 2026-09-26 00:28 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  57. 2026-09-24 19:33 UTCEG score recompute
  58. 2026-09-24 15:53 UTCEG score recompute
  59. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  60. 2026-09-23 21:32 UTCEG score recompute
  61. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  62. 2026-09-22 19:04 UTCEG score recompute
  63. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  64. 2026-09-21 22:37 UTCEG score recompute
  65. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  66. 2026-09-20 23:38 UTCEG score recompute
  67. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  68. 2026-09-19 17:27 UTCEG score recompute
  69. 2026-09-18 22:51 UTCEG score recompute
  70. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  71. 2026-09-17 21:09 UTCEG score recompute
  72. 2026-09-16 19:23 UTCEG score recompute
  73. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  74. 2026-09-16 09:25 UTCEG score recompute
  75. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 36th percentile

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-79675?
CVE-2026-79675 is a critical-severity vulnerability; its CVE record was published on August 25, 2026. 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…
When was CVE-2026-79675 made public?
CVE-2026-79675 was made public on August 11, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on August 25, 2026. EchelonGraph's copy of the record carries a last-modified date of September 1, 2026; the record at its source may have been updated since.
Is CVE-2026-79675 actively exploited?
CVE-2026-79675 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (54th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-79675?
CVE-2026-79675 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-79675?
A fix for CVE-2026-79675 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-79675 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-79675

Explore →

Is Your Infrastructure Affected by CVE-2026-79675?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs