Security control bypass via warning-only enforcement
Published Aug 22, 2026 · Updated Aug 22, 2026
Security control bypass in NLTK before 3.10.0 allows remote attackers to read local files through warning-only pathsec checks. The pathsec.py module initializes ENFORCE as false, so its validation functions emit RuntimeWarning messages and allow rejected file, network, ZIP, and pickle operations to continue. Exposure requires a consuming application to pass untrusted input into a guarded operation, and the resulting access remains limited by the Python process's permissions.
Summary
What happened
Security control bypass in NLTK before 3.10.0 allows remote attackers to read local files through warning-only pathsec checks. The pathsec.py module initializes ENFORCE as false, so its validation functions emit RuntimeWarning messages and allow rejected file, network, ZIP, and pickle operations to continue. Exposure requires a consuming application to pass untrusted input into a guarded operation, and the resulting access remains limited by the Python process's permissions.
The record
- CVE
- CVE-2026-62388
- Published
- Aug 22, 2026
- Updated
- Aug 22, 2026
- Vendor
- NLTK Project
- Product
- NLTK
- Classifications
- CWE-1188, T1005
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 22, 2026CVE publishedPublication date reported by the CVE source.
- Aug 22, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <3.10.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- pathsec ENFORCE warning-only proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo