NLTK versions before 3.10.3 contain a path traversal vulnerability in corpus readers that reopen root-derived paths using built-in open() instead of nltk.pathsec.open(), allowing symlinks to escape trusted roots. Attackers who stage symlinked corpus files under a trusted data root can disclose outside-root content through normal corpus reader methods like channels(), domains(), and synonyms().
CVE-2026-79676
Score 5.9 from GitHub Security Advisory (severity: HIGH) published 2026-08-25. a secondary CVSS source baseline 5.9; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.9
- EG Score
- 5.9(high)
- EG Risk
- 31(Track)EG Risk 31/100SSVC: Track
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 computedSeverity59% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 22%
- KEV
- Not listed
Published
August 25, 2026
Last Modified
August 28, 2026
Advisory Details (1)
Auto-updated Aug 25, 2026Corpus readers follow symlinks outside trusted roots despite pathsec enforcement · Advisory · nltk/nltk · GitHub
https://github.com/nltk/nltk/security/advisories/GHSA-p4rw-rvv2-7xwrVendor Advisories for CVE-2026-79676(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 14× in last 7d / 14× 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.
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 20:25 UTCEG score recompute
- 2026-08-29 20:25 UTCGHSA enrichment
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-28 19:07 UTCGHSA enrichment
- 2026-08-27 20:00 UTCEG score recompute
- 2026-08-27 20:00 UTCGHSA enrichment
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 18:43 UTCEG score recompute
- 2026-08-26 18:43 UTCGHSA enrichment
- 2026-08-26 14:47 UTCEPSS rescore
- 2026-08-25 16:24 UTCEG score recompute
- 2026-08-25 15:30 UTCEG score recompute
- 2026-08-25 15:29 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-79676?
When was CVE-2026-79676 disclosed?
Is CVE-2026-79676 actively exploited?
What is the CVSS score of CVE-2026-79676?
How do I remediate CVE-2026-79676?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-79676
Is Your Infrastructure Affected by CVE-2026-79676?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.