CVE-2026-62385
Path traversal in NLTK readers allows reading XML files outside corpus root.
Is CVE-2026-62385 being exploited?
Not confirmed. CVE-2026-62385 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.37% probability of exploitation in the next 30 days.
How severe is CVE-2026-62385?
CVE-2026-62385 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-62385?
Yes. A fix has been recorded for CVE-2026-62385. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-62385 affect?
CVE-2026-62385 affects NLTK < 3.10.0, FramenetCorpusReader, NKJPCorpusReader, Python apps using NLTK Framenet/NKJP modules. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-62385?
Upgrade NLTK to >=3.10.0; sanitize inputs and restrict file access.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attackers supplying crafted parameters to FramenetCorpusReader/NKJPCorpusReader can read arbitrary XML files accessible to the application, exposing sensitive data.
Patch when possible
- affected< 3.10.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.