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.

NLTK versions prior to 3.10.0 contain a critical misconfiguration in pathsec.py where the ENFORCE flag defaults to False. This causes all security validation functions to emit warnings rather than raising exceptions, effectively disabling security controls unless manually enabled by the user. As a result, attackers can bypass path traversal protections and pickle deserialization safeguards. The vulnerability stems from an insecure default configuration that places the burden of security activation on end users. Exploitation could lead to arbitrary file read/write via path traversal or remote code execution via unsafe pickle deserialization. The issue is resolved in NLTK version 3.10.0, which corrects the default enforcement behavior.