CVE-2026-65915

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreHIGH confidence

Score 6.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-22. a secondary CVSS source baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Elevated
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: Elevated riskExposed: 0

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

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.

CVSS v3
6.5
EG Score
6.5(high)
EG Risk
45(Track)
EG Risk 45/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
Severity65% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
30%
KEV
Not listed

Published

August 22, 2026

Last Modified

August 31, 2026

Advisory Details (2)

Auto-updated Aug 22, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

NLTK before 3.10.0 Arbitrary File Read via FileSystemPathPointer | Advisories | VulnCheck

https://www.vulncheck.com/advisories/nltk-before-arbitrary-file-read-via-filesystempathpointer
github Patch Available🟡 PoC Available

FileSystemPathPointer.open() sandbox check is dead code — arbitrary file read via file:// protocol · Advisory · nltk/nltk · GitHub

https://github.com/nltk/nltk/security/advisories/GHSA-72r2-7mfr-5xr9

Vendor Advisories for CVE-2026-65915(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.9.1-2, 3.9.2-1, 3.9.3-13.10.0-1—
PyPI(1)
PackageVulnerable rangeFixed inDependents
nltk0.8 ... 3.9b1 (65 versions)3.10.0—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 59× 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-18 21:37 UTCEG score recompute
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-17 21:15 UTCEG score recompute
  4. 2026-09-16 19:40 UTCEG score recompute
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-16 05:15 UTCEPSS rescore
  7. 2026-09-15 19:14 UTCEG score recompute
  8. 2026-09-13 21:19 UTCEG score recompute
  9. 2026-09-12 22:22 UTCEG score recompute
  10. 2026-09-11 23:26 UTCEG score recompute
  11. 2026-09-11 14:53 UTCEPSS rescore
  12. 2026-09-11 09:37 UTCEPSS rescore
  13. 2026-09-11 00:16 UTCEG score recompute
  14. 2026-09-09 01:42 UTCEG score recompute
  15. 2026-09-08 22:01 UTCEPSS rescore
  16. 2026-09-07 16:01 UTCEPSS rescore
  17. 2026-09-07 12:09 UTCEG score recompute
  18. 2026-09-06 13:47 UTCEPSS rescore
  19. 2026-09-06 13:00 UTCEG score recompute
  20. 2026-09-05 15:31 UTCEPSS rescore
  21. 2026-09-04 15:03 UTCEG score recompute
  22. 2026-09-04 05:07 UTCEPSS rescore
  23. 2026-09-02 16:46 UTCEG score recompute
  24. 2026-09-02 14:12 UTCEPSS rescore
  25. 2026-09-01 17:42 UTCEG score recompute
Show 34 more
  1. 2026-09-01 17:42 UTCGHSA enrichment
  2. 2026-09-01 13:54 UTCEPSS rescore
  3. 2026-09-01 04:40 UTCEPSS rescore
  4. 2026-08-31 18:44 UTCGHSA enrichment
  5. 2026-08-31 17:56 UTCEG score recompute
  6. 2026-08-31 17:55 UTCGHSA enrichment
  7. 2026-08-30 19:17 UTCEPSS rescore
  8. 2026-08-30 17:04 UTCEG score recompute
  9. 2026-08-30 17:04 UTCGHSA enrichment
  10. 2026-08-30 01:22 UTCEPSS rescore
  11. 2026-08-29 18:08 UTCEG score recompute
  12. 2026-08-29 18:07 UTCGHSA enrichment
  13. 2026-08-28 21:42 UTCEPSS rescore
  14. 2026-08-28 19:09 UTCGHSA enrichment
  15. 2026-08-28 18:03 UTCGHSA enrichment
  16. 2026-08-27 18:18 UTCEG score recompute
  17. 2026-08-27 18:18 UTCGHSA enrichment
  18. 2026-08-26 18:21 UTCEG score recompute
  19. 2026-08-26 18:20 UTCGHSA enrichment
  20. 2026-08-26 14:47 UTCEPSS rescore
  21. 2026-08-25 19:22 UTCEG score recompute
  22. 2026-08-25 19:22 UTCGHSA enrichment
  23. 2026-08-25 13:49 UTCEPSS rescore
  24. 2026-08-24 20:26 UTCEG score recompute
  25. 2026-08-24 20:26 UTCGHSA enrichment
  26. 2026-08-24 19:36 UTCEG score recompute
  27. 2026-08-24 19:36 UTCGHSA enrichment
  28. 2026-08-24 13:16 UTCEG score recompute
  29. 2026-08-24 13:16 UTCGHSA enrichment
  30. 2026-08-23 14:20 UTCEG score recompute
  31. 2026-08-23 14:20 UTCGHSA enrichment
  32. 2026-08-22 15:24 UTCEG score recompute
  33. 2026-08-22 14:26 UTCEG score recompute
  34. 2026-08-22 14:25 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-65915?
CVE-2026-65915 is a medium vulnerability published on August 22, 2026. 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…
When was CVE-2026-65915 disclosed?
CVE-2026-65915 was first published in the National Vulnerability Database on August 22, 2026, with the most recent update on August 31, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-65915 actively exploited?
CVE-2026-65915 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 70.4% of all scored CVEs.
What is the CVSS score of CVE-2026-65915?
CVE-2026-65915 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-65915?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-65915, 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-65915

Explore →

Is Your Infrastructure Affected by CVE-2026-65915?

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

Start Free Scan →Browse All CVEs