Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-63312: NLTK before 3.10.0 contains an arbitrary local file read vulnerability in StreamBackedCorpusView that bypasses

49
This week
HIGH 7.5REMOTEUPGRADE

CVE-2026-63312 is a high-severity flaw (CVSS 7.5) affecting nltk. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

  • High severity
  • Public exploit reference
  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score7.5 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance0.7% (top 49%)
CISA exploited listNo
WeaknessCWE-22
Published2026-08-22
Last modified2026-10-14
Publisher (CNA): VulnCheck · Vendor: nltk

Share: LinkedIn · X · Reddit

Last updated 2026-10-14 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

nltk nltk UPGRADE
Affected: < 3.10.0
Fixed in: 3.10.0
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy nltk || rpm -q nltk || nltk --version
2. UPGRADE to 3.10.0 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade nltk
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade nltk
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-63312?

nltk: upgrade to 3.10.0. Exact commands for each OS are on this page.

Is CVE-2026-63312 being exploited?

CVE-2026-63312 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-63312 affect?

CVE-2026-63312 affects nltk. Severity is high (CVSS 7.5). 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

How urgent is CVE-2026-63312?

Priority 49/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.