NLTK versions before 3.10.0 contain a path traversal vulnerability in FramenetCorpusReader and NKJPCorpusReader that allows attackers to parse XML files outside the corpus root by supplying unsafe selectors or poisoned index state. Attackers can exploit frame_by_name, doc, lu, and header methods with crafted parameters to read arbitrary XML files accessible to the application.
CVE-2026-62385
Score 5.9 from GitHub Security Advisory (severity: HIGH) published 2026-08-22. 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
- 43(Track)EG Risk 43/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%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 21%
- KEV
- Not listed
Published
August 22, 2026
Last Modified
August 24, 2026
Advisory Details (2)
Auto-updated Aug 22, 2026NLTK 3.9.4 Path Traversal via FrameNet and NKJP Readers | Advisories | VulnCheck
https://www.vulncheck.com/advisories/nltk-path-traversal-via-framenet-and-nkjp-readersStable FrameNet and NKJP readers parse outside-root XML in 3.9.4 · Advisory · nltk/nltk · GitHub
Affected: version 3.10.0, which includes the path-safety rejections seen in the release can
https://github.com/nltk/nltk/security/advisories/GHSA-568f-pv23-39p4Vendor Advisories for CVE-2026-62385(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 12× in last 7d / 12× 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-25 22:34 UTCEG score recompute
- 2026-08-25 22:34 UTCGHSA enrichment
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 20:26 UTCEG score recompute
- 2026-08-24 20:26 UTCGHSA enrichment
- 2026-08-24 19:22 UTCEG score recompute
- 2026-08-24 19:22 UTCGHSA enrichment
- 2026-08-23 17:30 UTCEG score recompute
- 2026-08-23 17:30 UTCGHSA enrichment
- 2026-08-22 15:24 UTCEG score recompute
- 2026-08-22 14:26 UTCEG score recompute
- 2026-08-22 14:25 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-62385?
When was CVE-2026-62385 disclosed?
Is CVE-2026-62385 actively exploited?
What is the CVSS score of CVE-2026-62385?
How do I remediate CVE-2026-62385?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-62385
Is Your Infrastructure Affected by CVE-2026-62385?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.