CVE-2026-79657

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 1.5% (75th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated

Also known asEUVD-2026-65440 (ENISA EUVD) · GHSA-vp9c-2pjm-8925 (GitHub Security Advisories) · GHSA-x99w-6fgc-pmfw (GitHub Security Advisories) · PYSEC-2026-3735 (OSV.dev)Source: ENISA EUVD

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: 1.5%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

NLTK versions before 3.10.3 contain a remote code execution vulnerability in allowlisted pickle loaders that trust entire module namespaces instead of specific safe callables. Attackers can craft malicious pickle payloads invoking dangerous in-namespace functions like ReppTokenizer._execute and numpy.f2py.crackfortran.myeval through pickle REDUCE to execute arbitrary commands during model or tokenizer artifact loading.

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 impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
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
1.5%
EPSS %ILE
75th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
1.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

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.

The score's inputs: 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

October 8, 2026

Advisory Details (2)

Auto-updated Nov 8, 2026
🔬 Proof of concept available. Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

Allowlisted pickle loaders still permit code execution in current source · Advisory · nltk/nltk · GitHub

https://github.com/nltk/nltk/security/advisories/GHSA-x99w-6fgc-pmfw
Web page

NLTK before 3.10.3 Remote Code Execution via Unsafe Pickle Deserialization | Advisories | VulnCheck

https://www.vulncheck.com/advisories/nltk-before-3.10.3-remote-code-execution-via-unsafe-pickle-deserialization

Vendor Advisories for CVE-2026-79657(2)

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

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-trustyai-garak-lls-provider-dsp-rhel9:17917858042026-10-19redhat
pipnltk @ 3.10.3 (fixes <= 3.10.2)—ghsa

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(2)

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

Data Freshness Timeline

(refreshed 19× in last 7d / 64× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 248 rows 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 148 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-79657?
CVE-2026-79657 is a critical-severity vulnerability; its CVE record was published on August 25, 2026. NLTK versions before 3.10.3 contain a remote code execution vulnerability in allowlisted pickle loaders that trust entire module namespaces instead of specific safe callables. Attackers can craft malicious pickle payloads invoking dangerous in-namespace functions like ReppTokenizer._execute and…
When was CVE-2026-79657 made public?
CVE-2026-79657 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 October 8, 2026; the record at its source may have been updated since.
Is CVE-2026-79657 actively exploited?
CVE-2026-79657 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.5% probability of exploitation in the next 30 days (75th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-79657?
CVE-2026-79657 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-79657?
A fix for CVE-2026-79657 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-79657 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-79657

Explore →

Is Your Infrastructure Affected by CVE-2026-79657?

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