CVE-2026-62388
NLTK default disable of pathsec protections allows path traversal and pickle-based RCE.
Is CVE-2026-62388 being exploited?
Not confirmed. CVE-2026-62388 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.46% probability of exploitation in the next 30 days.
How severe is CVE-2026-62388?
CVE-2026-62388 is rated High with a CVSS score of 8.7. 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-62388?
Yes. A fix has been recorded for CVE-2026-62388. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-62388 affect?
CVE-2026-62388 affects NLTK < 3.10.0, Python apps using NLTK pathsec.py, Systems deserializing pickled data via NLTK. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-62388?
Upgrade NLTK to >=3.10.0, set ENFORCE=True, audit deserialization use.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attackers can bypass path traversal and pickle deserialization protections to achieve remote code execution via crafted inputs.
Immediate action required
- 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.