CVE-2026-71514

LOWNVD 3.33.3
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 3.3 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 94% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
3.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 3.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
3.3
EG Score
3.3(medium)
EG Risk
15(Track)
EG Risk 15/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity33% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

August 22, 2026

Last Modified

September 2, 2026

Vendor Advisories for CVE-2026-71514(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
nltk3.10.0-1 ... 3.9.3-1 (9 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
nltk3.10.0-1 ... 3.9.3-1 (6 versions)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
nltk3.10.0-1, 3.10.1-1, 3.9.1-2, 3.9.2-1, 3.9.3-13.10.3-1
PyPI(1)
PackageVulnerable rangeFixed inDependents
nltk3.10.0, 3.10.1, 3.10.2, 3.9.43.10.3

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 38× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-19 06:52 UTCEG score recompute
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-16 14:08 UTCEPSS rescore
  4. 2026-09-16 12:35 UTCEG score recompute
  5. 2026-09-16 05:15 UTCEPSS rescore
  6. 2026-09-15 03:12 UTCEPSS rescore
  7. 2026-09-13 18:28 UTCEG score recompute
  8. 2026-09-12 15:02 UTCEPSS rescore
  9. 2026-09-11 14:53 UTCEPSS rescore
  10. 2026-09-11 00:20 UTCEG score recompute
  11. 2026-09-10 09:35 UTCEPSS rescore
  12. 2026-09-08 22:01 UTCEPSS rescore
  13. 2026-09-08 06:13 UTCEG score recompute
  14. 2026-09-06 13:48 UTCEPSS rescore
  15. 2026-09-05 12:03 UTCEG score recompute
  16. 2026-09-04 05:07 UTCEPSS rescore
  17. 2026-09-02 17:55 UTCEG score recompute 0.80
  18. 2026-09-02 17:53 UTCNVD updateCVSS v3 → 3.3
  19. 2026-09-02 14:12 UTCEPSS rescore
  20. 2026-09-01 13:54 UTCEPSS rescore
  21. 2026-09-01 04:40 UTCEPSS rescore
  22. 2026-08-31 14:06 UTCEG score recompute
  23. 2026-08-31 14:05 UTCGHSA enrichment
  24. 2026-08-30 19:17 UTCEPSS rescore
  25. 2026-08-30 01:22 UTCEPSS rescore
Show 13 more
  1. 2026-08-28 21:42 UTCEPSS rescore
  2. 2026-08-28 19:12 UTCGHSA enrichment
  3. 2026-08-27 14:36 UTCEG score recompute
  4. 2026-08-27 14:36 UTCGHSA enrichment
  5. 2026-08-26 14:47 UTCEPSS rescore
  6. 2026-08-25 13:49 UTCEPSS rescore
  7. 2026-08-24 20:27 UTCEG score recompute
  8. 2026-08-24 20:26 UTCGHSA enrichment
  9. 2026-08-24 19:22 UTCEG score recompute
  10. 2026-08-24 19:22 UTCGHSA enrichment
  11. 2026-08-22 14:22 UTCEG score recompute
  12. 2026-08-22 13:46 UTCEG score recompute
  13. 2026-08-22 13:45 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-71514?
CVE-2026-71514 is a low vulnerability published on August 22, 2026. NLTK 3.9.4 through 3.10.2 contains a path traversal vulnerability in CrubadanCorpusReader. loadlangngrams joins the corpus root with crubadancode, 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,…
When was CVE-2026-71514 disclosed?
CVE-2026-71514 was first published in the National Vulnerability Database on August 22, 2026, with the most recent update on September 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-71514 actively exploited?
CVE-2026-71514 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 94.2% of all scored CVEs.
What is the CVSS score of CVE-2026-71514?
CVE-2026-71514 has a CVSS v3 base score of 3.3 (NVD).
How do I remediate CVE-2026-71514?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-71514, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-71514

Explore →

Is Your Infrastructure Affected by CVE-2026-71514?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.