High [CVE-2026-62388] Bypass of path traversal and pickle deserialization protections due to insecure default configuration
This high-severity Red Hat Linux advisory covers CVE-2026-62388 affecting Lightspeed Core, Red Hat Ansible Automation Platform 2.
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
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.
A flaw was found in NLTK. The software's default settings in `pathsec.py` cause security checks to only issue warnings rather than actively preventing malicious actions.
This allows attackers to bypass safeguards designed to prevent unauthorized access to files (path traversal) and the execution of harmful code through data processing (pickle deserialization). NLTK versions before 3.10.0 in Red Hat products are configured by default to not enforce security validations for path traversal and pickle deserialization.
This insecure default allows attackers to bypass these protections, as security controls are only active when manually enabled, increasing the risk of arbitrary code execution or unauthorized file access. Red Hat severity: Important — CVSS 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N).
Weakness: CWE-1188. Affected Red Hat products: Lightspeed Core; Red Hat Ansible Automation Platform 2.
Red Hat lists Exploit Intelligence; OpenShift Lightspeed; Red Hat OpenShift AI (RHOAI) as not affected.
- < 3.10.0
Official advisory · high-confidence parse· fetched 1 hour ago·verify at source
Fixed versions
No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.
Official advisory · high-confidence parse· fetched 1 hour ago·verify at source
Mitigation checklist
- To mitigate this issue, ensure that the NLTK security validation enforcement is enabled. This can be achieved by setting `nltk.internals.pathsec.ENFORCE = True` in your application's initialization code before processing untrusted data. This change may require restarting any services or applications that utilize NLTK.
Official advisory · high-confidence parse· fetched 1 hour ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.