NLTK before 3.10.0 contains an arbitrary local file read vulnerability in StreamBackedCorpusView that bypasses pathsec.ENFORCE by calling builtins.open() directly inst…

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

1. Aug 22, 2026 · NIST NVD

   Detected

   NLTK before 3.10.0 contains an arbitrary local file read vulnerability in StreamBackedCorpusView that bypasses pathsec.ENFORCE by calling builtins.open() directly instead of pathsec.open(). Attackers who control the fileid argument can read arbitrary local files regardless of the ENFORCE setting, including sensitive system files and application credentials.

2. Oct 14, 2026 · NIST NVD

   Updated

   NLTK before 3.10.0 contains an arbitrary local file read vulnerability in StreamBackedCorpusView that bypasses pathsec.ENFORCE by calling builtins.open() directly instead of pathsec.open(). Attackers who control the fileid argument can read arbitrary local files regardless of the ENFORCE setting, including sensitive system files and application credentials.

Affected

• cpe nltk/nltkversion unspecified

Sources

• CVE.orgVulnerability recordCVE-2026-63312

  Official CVE identifier

  cve.org
• FIRST EPSSExploitation probabilityCVE-2026-63312

  30-day exploitation probability 0.7%

  first.org
• NIST NVDVulnerability recordCVE-2026-63312

  NLTK before 3.10.0 contains an arbitrary local file read vulnerability in StreamBackedCorpusView that bypasses pathsec.ENFORCE by calling builtins.open() directly instead of pathsec.open(). Attackers who control the fileid argument can read arbitrary local files regardless of the

  nvd.nist.gov

References

• Exploit · github.com
• Third Party Advisory · vulncheck.com