CVE-2026-65915 NLTK before 3.10.0 Arbitrary File Read via FileSystemPathPointer

High 7.1 Published Updated

Attackers can read arbitrary files by exploiting a broken sandbox check in NLTK's FileSystemPathPointer, potentially exposing sensitive credentials and configuration data.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2026-65915?

CVE-2026-65915 is a high-severity path traversal vulnerability in nltk, published on 22 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

NLTK versions before 3.10.0 contain a logic bug in FileSystemPathPointer.open() where the sandbox validation check compares a normalized path against itself, making the security check permanently inert. Attackers can pass file:// URLs to nltk.data.load() to read arbitrary files accessible to the process user, including credentials and configuration files.

Weakness: CWE-284

Which versions are affected by CVE-2026-65915?

3 open source packages ship an affected version, including nltk. It affects 1 product.

PackageAffectedFixed in
nltk PyPIAll versions3.10.0
nltk PyPIAll versions3.10.0
nltk PyPIAll versions3.10.0

Products include Nltk Nltk.

How do I fix CVE-2026-65915?

Upgrade nltk to 3.10.0 or later.

Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.

Is CVE-2026-65915 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-65915 exists.

Sources

Also known as DEBIAN-CVE-2026-65915, ECHO-c5e2-d7e8-d8ea, GHSA-72r2-7mfr-5xr9, MINI-4x5j-m67q-3rfc, PYSEC-2026-3731, UBUNTU-CVE-2026-65915.

Is CVE-2026-65915 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free