CVE-2026-79674

HIGHPre-NVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.2Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

NLTK versions before 3.10.3 contain a path sandbox bypass vulnerability in corpus-reader constructors that allows attackers to read files outside the intended data root. Attackers can supply arbitrary corpus root paths to LinThesaurusCorpusReader and PanLexLiteCorpusReader constructors to access filesystem content and SQLite databases outside the pathsec sandbox boundary.

CVSS v3
8.2
EG Score
8.2HIGHmedium confidence
EG Risk
68
EG Risk 68/100CISA SSVC

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
Severity82% × 45%
Exploitation40% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
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.4%
EPSS %ILE
30th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

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 partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 25, 2026

Last Modified

August 31, 2026

Advisory Details (1)

Auto-updated Aug 25, 2026
🔬 Proof of concept available. Patch available. Sources: github.
githubMentions a patch (unverified)🟡 PoC Available

Corpus Reader Sandbox Bypass · Advisory · nltk/nltk · GitHub

https://github.com/nltk/nltk/security/advisories/GHSA-3gq4-3j92-5w49

Patch Availability(2)

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

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 21× in last 7d / 82× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 131 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-79674?
CVE-2026-79674 is a high vulnerability published on August 25, 2026. NLTK versions before 3.10.3 contain a path sandbox bypass vulnerability in corpus-reader constructors that allows attackers to read files outside the intended data root. Attackers can supply arbitrary corpus root paths to LinThesaurusCorpusReader and PanLexLiteCorpusReader constructors to access…
When was CVE-2026-79674 disclosed?
CVE-2026-79674 was first published on August 25, 2026, with the most recent update on August 31, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-79674 actively exploited?
CVE-2026-79674 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (30th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-79674?
CVE-2026-79674 has a CVSS base score of 8.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-79674?
A fix for CVE-2026-79674 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-79674 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-79674

Explore →

Is Your Infrastructure Affected by CVE-2026-79674?

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