NLTK versions before 3.10.0 default to ENFORCE=False in pathsec.py, causing all security validation functions to emit warnings instead of raising exceptions.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

1. Aug 22, 2026 · NIST NVD

   Detected

   NLTK versions before 3.10.0 default to ENFORCE=False in pathsec.py, causing all security validation functions to emit warnings instead of raising exceptions. Attackers can bypass path traversal and pickle deserialization protections by exploiting the disabled security controls that are only active when manually enabled.

2. Oct 14, 2026 · NIST NVD

   Updated

   NLTK versions before 3.10.0 default to ENFORCE=False in pathsec.py, causing all security validation functions to emit warnings instead of raising exceptions. Attackers can bypass path traversal and pickle deserialization protections by exploiting the disabled security controls that are only active when manually enabled.

Affected

• cpe nltk/nltkversion unspecified

Sources

• CVE.orgVulnerability recordCVE-2026-62388

  Official CVE identifier

  cve.org
• FIRST EPSSExploitation probabilityCVE-2026-62388

  30-day exploitation probability 0.5%

  first.org
• NIST NVDVulnerability recordCVE-2026-62388

  NLTK versions before 3.10.0 default to ENFORCE=False in pathsec.py, causing all security validation functions to emit warnings instead of raising exceptions. Attackers can bypass path traversal and pickle deserialization protections by exploiting the disabled security controls th

  nvd.nist.gov

References

• Exploit · github.com
• Third Party Advisory · vulncheck.com