NLTK versions before 3.10.0 default to ENFORCE=False in pathsec.py, causing all security validation functions to emit warnings instead of raising… (CVE-2026-62388)
NLTK versions before 3.10.0 have a security vulnerability where the default setting ENFORCE=False in pathsec.py causes security validation functions to emit warnings instead of raising exceptions. This behavior disables important protections against path traversal and pickle deserialization attacks unless manually enabled. The vulnerability has a high severity score of 7.5 and affects all versions prior to 3.10.0.
AI Analysis
Technical Summary
In NLTK versions before 3.10.0, the pathsec.py module defaults the ENFORCE setting to False. This causes security validation functions to only emit warnings rather than raising exceptions when validation fails. As a result, protections against path traversal and pickle deserialization attacks can be bypassed if the security controls are not manually enabled. This vulnerability is tracked as CVE-2026-62388 with a CVSS 3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N), indicating a high severity remote vulnerability that can lead to confidentiality impact without requiring privileges or user interaction.
Potential Impact
Attackers can bypass path traversal and pickle deserialization protections in affected NLTK versions by exploiting the disabled security controls that only activate when ENFORCE is manually set to True. This can lead to unauthorized access to sensitive data or execution of malicious deserialization payloads, impacting confidentiality. There is no indication of integrity or availability impact. The vulnerability is remotely exploitable without authentication or user interaction.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should manually enable the ENFORCE setting in pathsec.py to ensure security validation functions raise exceptions rather than just warnings, thereby restoring protections against path traversal and pickle deserialization attacks.
NLTK versions before 3.10.0 default to ENFORCE=False in pathsec.py, causing all security validation functions to emit warnings instead of raising… (CVE-2026-62388)
Description
NLTK versions before 3.10.0 have a security vulnerability where the default setting ENFORCE=False in pathsec.py causes security validation functions to emit warnings instead of raising exceptions. This behavior disables important protections against path traversal and pickle deserialization attacks unless manually enabled. The vulnerability has a high severity score of 7.5 and affects all versions prior to 3.10.0.
CVSS v3.1
Score 7.5high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
In NLTK versions before 3.10.0, the pathsec.py module defaults the ENFORCE setting to False. This causes security validation functions to only emit warnings rather than raising exceptions when validation fails. As a result, protections against path traversal and pickle deserialization attacks can be bypassed if the security controls are not manually enabled. This vulnerability is tracked as CVE-2026-62388 with a CVSS 3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N), indicating a high severity remote vulnerability that can lead to confidentiality impact without requiring privileges or user interaction.
Potential Impact
Attackers can bypass path traversal and pickle deserialization protections in affected NLTK versions by exploiting the disabled security controls that only activate when ENFORCE is manually set to True. This can lead to unauthorized access to sensitive data or execution of malicious deserialization payloads, impacting confidentiality. There is no indication of integrity or availability impact. The vulnerability is remotely exploitable without authentication or user interaction.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should manually enable the ENFORCE setting in pathsec.py to ensure security validation functions raise exceptions rather than just warnings, thereby restoring protections against path traversal and pickle deserialization attacks.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-8vh5-mgjj-w6hg
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-62388"]
- Ecosystems
- []
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6a8a27f9acd9273b499bc9ca
Added to database: 08/22/2026, 22:51:37 UTC
Last enriched: 08/22/2026, 22:52:17 UTC
Last updated: 08/23/2026, 00:29:42 UTC
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.