Skip to content
Noroxi
NVD / CVE Program· CNA VulnCheck

CVE-2026-71514: NLTK 3.9.4 through 3.10.2 Path Traversal via CrubadanCorpusReader pathsec Bypass

LowCVSS 2.0 · v4.0—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 8/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
  • Someone with local access to the system can trigger it. No account or password is required. Special conditions such as timing or configuration are required.
  • Fixed version: nltk nltk 3.10.3.

Low priority for now. Upgrade to nltk nltk 3.10.3 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

NLTK 3.9.4 through 3.10.2 contains a path traversal vulnerability in CrubadanCorpusReader. _load_lang_ngrams joins the corpus root with crubadan_code, the column-0 value read from the corpus table.txt mapping file, and opens the result with the builtin open() rather than the pathsec-validated opener, so os.path.join discards the root when that value is absolute and the read escapes the corpus directory without the containment check nltk.pathsec applies when ENFORCE is set. An attacker who controls a corpus package can disclose file contents outside the corpus root through lang_freq, limited to paths ending in -3grams.txt whose contents parse as token count lines.

Published
Aug 22, 2026
Updated
Oct 14, 2026
EPSS
0.1% · 6th percentile

Report tools

JSON

Action score

8

Monitor

Low priority for now.

CVSS
8 / 40 · 2.0 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · VulnCheck
2.0
NVD has not scored this yet; the score shown is the CNA’s.

CVSS:4.0/AV:L/AC:H/AT:P/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-71514

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
nltknltk

Versions reported by the vendor

Affected version ranges reported by the assigning authority (VulnCheck). Independent of NVD's CPE analysis and usually ahead of it.

  • nltk nltk

    • 3.10.3not affected
    • 3.9.4 and later · before 3.10.3affected · semver

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • nltk nltk3.9.4 and later · up to 3.10.2 inclusive

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12nltkfrom 0—
Debian:14nltkbefore 3.10.3-13.10.3-1
PyPInltkfrom 3.9.4 · before 3.10.33.10.3

Same product

nltk: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-0848Arbitrary Code Execution in NLTK StanfordSegmenter via Untrusted JAR Loading
    40Plan
  • CVE-2026-79675NLTK before 3.10.3 JVM Argument Injection via Per-Call Options
    37Monitor
  • CVE-2026-79657NLTK before 3.10.3 Remote Code Execution via Unsafe Pickle Deserialization
    37Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2026-72818Aug 20, 2026 · NLTK TweetTokenizer URL Pattern Backtracks Catastrophically on Naked-Domain-Like Input
    34Monitor
  • ← EarlierCVE-2026-71513Aug 22, 2026 · NLTK 3.10.0 through 3.10.2 Remote Code Execution via AllowlistUnpickler Dotted-Name Bypass
    34Monitor
  • Later →CVE-2026-62383Aug 22, 2026 · nltk IPIPANCorpusReader Symlink Arbitrary File Read
    27Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
nltk nltk3.10.3Vendor (CNA)
debian:nltk3.10.3-1 · Debian:14Package registry (OSV)
PyPI:nltk3.10.3Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-623840 days apartNLTK FramenetCorpusReader Symlink Sandbox Bypass before 3.10.2
    34Monitor
  • CVE-2026-633120 days apartNLTK StreamBackedCorpusView Bypasses pathsec.ENFORCE Arbitrary File Read
    34Monitor
  • CVE-2026-10995652 days apartNLTK through 3.10.3 Path Traversal via WekaClassifier Model Path
    33Monitor
  • CVE-2026-796763 days apartNLTK before 3.10.3 Path Traversal via Symlink Bypass
    32Monitor
  • CVE-2026-33236155 days apartNLTK has a Downloader Path Traversal Vulnerability (AFO) - Arbitrary File Overwrite
    32Monitor
  • CVE-2026-5429361 days apartNLTK: URL-Encoded Path Traversal in nltk.data.load() Allows Arbitrary Local File Read
    30Monitor

Not on record for this CVE: public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • No account or password is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
Integrity
Availability
Attack vector
Local
Attack complexity
High
Privileges required
None
User interaction
P
Scope
X

CVSS vector

CVSS:4.0/AV:L/AC:H/AT:P/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

nvd-secondary

Root cause

A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
const file = path.join(ROOT, req.query.name);res.sendFile(file);

Fixed

ts
const file = path.resolve(ROOT, req.query.name);if (!file.startsWith(ROOT + path.sep)) {  return res.sendStatus(400);}res.sendFile(file);

References

All records