CVE-2026-71514

LOWNVD 3.33.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This low-severity CVE scores 3.3 under NVD CVSS v3. EPSS exploit probability: 0.2% (6th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 2.5 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-08-22) is not newer than that change (2026-09-02), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
3.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 3.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.3LOWmedium confidence
EG Risk
15
EG Risk 15/100

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 (value × EchelonGraph’s weight)
Severity33% × 45%
The EG Score, 3.3 of 10.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
6th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 22, 2026

Last Modified

September 2, 2026

References (4)

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 rangeFix by version rangeDependents
nltk3.10.0-1 ... 3.9.3-1 (9 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
nltk3.10.0-1 ... 3.9.3-1 (6 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
nltk3.10.0-1, 3.10.1-1, 3.9.1-2, 3.9.2-1, 3.9.3-1
  • every version up to 3.10.3-1: fixed in 3.10.3-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
nltk3.10.0, 3.10.1, 3.10.2, 3.9.4
  • 3.9.4 up to 3.10.3: fixed in 3.10.3
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 36× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  3. 2026-10-12 15:42 UTCEG score recompute
  4. 2026-10-11 19:28 UTCEG score recompute
  5. 2026-10-11 16:43 UTCEG score recompute
  6. 2026-10-11 14:03 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  10. 2026-10-09 05:34 UTCEG score recompute
  11. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  12. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  13. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  14. 2026-10-05 19:47 UTCEG score recompute
  15. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  16. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  17. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  18. 2026-10-03 01:40 UTCEG score recompute
  19. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  20. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  21. 2026-09-30 07:33 UTCEG score recompute
  22. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  23. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  24. 2026-09-27 13:14 UTCEG score recompute
  25. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 5th percentile
Show 43 more
  1. 2026-09-24 19:07 UTCEG score recompute
  2. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  3. 2026-09-22 01:00 UTCEG score recompute
  4. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  5. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  6. 2026-09-19 06:52 UTCEG score recompute
  7. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  8. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  9. 2026-09-16 12:35 UTCEG score recompute
  10. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  11. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  12. 2026-09-13 18:28 UTCEG score recompute
  13. 2026-09-12 15:02 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  14. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  15. 2026-09-11 00:20 UTCEG score recompute
  16. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  17. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  18. 2026-09-08 06:13 UTCEG score recompute
  19. 2026-09-06 13:48 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  20. 2026-09-05 12:03 UTCEG score recompute
  21. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  22. 2026-09-02 17:55 UTCEG score recompute▲ 0.80
  23. 2026-09-02 17:53 UTCNVD updateCVSS v3 → 3.3
  24. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  25. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  26. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  27. 2026-08-31 14:06 UTCEG score recompute
  28. 2026-08-31 14:05 UTCGHSA enrichmentGHSA-cv22-g7mw-8v73 · GitHub severity LOW · GitHub CVSS 2.5
  29. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  30. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  31. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  32. 2026-08-28 19:12 UTCGHSA enrichmentGHSA-cv22-g7mw-8v73 · GitHub severity LOW · GitHub CVSS 2.5
  33. 2026-08-27 14:36 UTCEG score recompute
  34. 2026-08-27 14:36 UTCGHSA enrichmentGHSA-cv22-g7mw-8v73 · GitHub severity LOW · GitHub CVSS 2.5
  35. 2026-08-26 14:47 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  36. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  37. 2026-08-24 20:27 UTCEG score recompute
  38. 2026-08-24 20:26 UTCGHSA enrichmentGHSA-cv22-g7mw-8v73 · GitHub severity LOW · GitHub CVSS 2.5
  39. 2026-08-24 19:22 UTCEG score recompute
  40. 2026-08-24 19:22 UTCGHSA enrichmentGHSA-cv22-g7mw-8v73 · GitHub severity LOW · GitHub CVSS 2.5
  41. 2026-08-22 14:22 UTCEG score recompute
  42. 2026-08-22 13:46 UTCEG score recomputeFirst assessed: 2.5 LOW
  43. 2026-08-22 13:45 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-71514?
CVE-2026-71514 is a low-severity vulnerability; its CVE record was 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 made public?
CVE-2026-71514 was made public on August 11, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on August 22, 2026. EchelonGraph's copy of the record carries a last-modified date of September 2, 2026; the record at its source may have been updated since.
Is CVE-2026-71514 actively exploited?
CVE-2026-71514 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-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?
A fix for CVE-2026-71514 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-71514 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs