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.
References
| Link | Resource |
|---|---|
| https://github.com/nltk/nltk/security/advisories/GHSA-p3m8-78j2-g5p3 | Exploit Mitigation Vendor Advisory |
| https://www.vulncheck.com/advisories/nltk-before-insecure-default-configuration-pathsec | Third Party Advisory |
| https://github.com/nltk/nltk/security/advisories/GHSA-p3m8-78j2-g5p3 | Exploit Mitigation Vendor Advisory |
Configurations
History
No history.
Information
Published : 2026-08-22 15:16
Updated : 2026-08-27 19:54
NVD link : CVE-2026-62388
Mitre link : CVE-2026-62388
CVE.ORG link : CVE-2026-62388
JSON object : View
Products Affected
nltk
- nltk
CWE
CWE-1188
Initialization of a Resource with an Insecure Default
