CVE-2026-54293

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Elevated
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

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

NLTK (Natural Language Toolkit) is a suite of open source Python modules, data sets, and tutorials supporting research and development in Natural Language Processing. Prior to 3.10.0-rc1, nltk.data.load() in NLTK is vulnerable to path traversal via URL-encoded path separators and traversal segments when using the nltk: URL scheme. The unsafe-path regex check is performed before url2pathname() decodes the %xx sequences (a classic decode-after-check / TOCTOU-style flaw), allowing an attacker to bypass the protection documented in NLTK's SECURITY.md and read arbitrary files from the filesystem. While literal traversal strings such as ../../../etc/passwd are correctly blocked, encoded variants such as %2fetc%2fpasswd, %2e%2e%2f..., and ..%2f..%2f slip past the regex and are subsequently decoded into a real filesystem path. This vulnerability is fixed in 3.10.0-rc1.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
33.2%
KEV
Not listed

Published

June 16, 2026

Last Modified

July 21, 2026

Advisory Details (2)

Auto-updated Jun 22, 2026
🔬 Proof of concept available. Patch available. Sources: github_pr, github.
github Patch Available🟡 PoC Available

URL-Encoded Path Traversal in nltk.data.load() Allows Arbitrary Local File Read · Advisory · nltk/nltk · GitHub

https://github.com/nltk/nltk/security/advisories/GHSA-p4gq-832x-fm9v
github_pr Patch Available

fix(security): block URL-encoded path traversal in nltk: resource URLs

Patch available: nltk/nltk v3.10.0-rc1 (PR #3575 merged 2026-06-06)

https://github.com/nltk/nltk/pull/3575

Vendor Advisories for CVE-2026-54293(2)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
pipnltk—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
nltk0.8 ... 3.9b1 (65 versions)——

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 86× 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-07-22 14:08 UTCEPSS rescore
  2. 2026-07-21 15:25 UTCEPSS rescore
  3. 2026-07-20 17:08 UTCEPSS rescore
  4. 2026-07-19 14:31 UTCEPSS rescore
  5. 2026-07-19 14:31 UTCEPSS rescore
  6. 2026-07-19 02:29 UTCEPSS rescore
  7. 2026-07-18 10:04 UTCEPSS rescore
  8. 2026-07-16 17:03 UTCEPSS rescore
  9. 2026-07-16 09:36 UTCGHSA enrichment
  10. 2026-07-15 20:32 UTCGHSA enrichment
  11. 2026-07-15 16:57 UTCEPSS rescore
  12. 2026-07-15 16:57 UTCEPSS rescore
  13. 2026-07-15 07:27 UTCGHSA enrichment
  14. 2026-07-15 02:00 UTCEPSS rescore
  15. 2026-07-15 02:00 UTCEPSS rescore
  16. 2026-07-14 18:21 UTCGHSA enrichment
  17. 2026-07-14 05:01 UTCGHSA enrichment
  18. 2026-07-13 22:31 UTCEPSS rescore
  19. 2026-07-13 15:55 UTCGHSA enrichment
  20. 2026-07-13 06:13 UTCEPSS rescore
  21. 2026-07-13 06:13 UTCEPSS rescore
  22. 2026-07-13 02:48 UTCGHSA enrichment
  23. 2026-07-12 13:43 UTCGHSA enrichment
  24. 2026-07-12 05:46 UTCEPSS rescore
  25. 2026-07-12 00:13 UTCGHSA enrichment
Show 74 more
  1. 2026-07-11 11:08 UTCGHSA enrichment
  2. 2026-07-11 08:27 UTCEPSS rescore
  3. 2026-07-11 08:27 UTCEPSS rescore
  4. 2026-07-10 22:04 UTCGHSA enrichment
  5. 2026-07-10 09:00 UTCGHSA enrichment
  6. 2026-07-09 19:56 UTCGHSA enrichment
  7. 2026-07-09 19:10 UTCEPSS rescore
  8. 2026-07-09 19:10 UTCEPSS rescore
  9. 2026-07-09 03:56 UTCGHSA enrichment
  10. 2026-07-08 15:16 UTCEPSS rescore
  11. 2026-07-08 15:16 UTCEPSS rescore
  12. 2026-07-08 14:52 UTCGHSA enrichment
  13. 2026-07-08 01:46 UTCGHSA enrichment
  14. 2026-07-07 13:46 UTCEPSS rescore
  15. 2026-07-07 13:46 UTCEPSS rescore
  16. 2026-07-07 12:41 UTCGHSA enrichment
  17. 2026-07-06 23:15 UTCGHSA enrichment
  18. 2026-07-06 16:27 UTCEPSS rescore
  19. 2026-07-06 16:27 UTCEPSS rescore
  20. 2026-07-06 02:23 UTCEPSS rescore
  21. 2026-07-06 02:23 UTCEPSS rescore
  22. 2026-07-06 00:37 UTCGHSA enrichment
  23. 2026-07-05 11:32 UTCGHSA enrichment
  24. 2026-07-05 02:31 UTCEPSS rescore
  25. 2026-07-05 02:30 UTCEPSS rescore
  26. 2026-07-04 22:26 UTCGHSA enrichment
  27. 2026-07-04 09:21 UTCGHSA enrichment
  28. 2026-07-04 06:31 UTCEPSS rescore
  29. 2026-07-04 06:31 UTCEPSS rescore
  30. 2026-07-03 14:49 UTCGHSA enrichment
  31. 2026-07-03 01:45 UTCGHSA enrichment
  32. 2026-07-02 12:39 UTCGHSA enrichment
  33. 2026-07-01 23:28 UTCGHSA enrichment
  34. 2026-07-01 15:07 UTCEPSS rescore
  35. 2026-07-01 10:24 UTCGHSA enrichment
  36. 2026-06-30 23:22 UTCEPSS rescore
  37. 2026-06-30 21:20 UTCGHSA enrichment
  38. 2026-06-30 08:15 UTCGHSA enrichment
  39. 2026-06-29 19:11 UTCGHSA enrichment
  40. 2026-06-29 14:06 UTCEPSS rescore
  41. 2026-06-29 14:06 UTCEPSS rescore
  42. 2026-06-29 06:07 UTCGHSA enrichment
  43. 2026-06-28 17:02 UTCGHSA enrichment
  44. 2026-06-28 14:07 UTCEPSS rescore
  45. 2026-06-28 04:56 UTCEPSS rescore
  46. 2026-06-28 04:56 UTCEPSS rescore
  47. 2026-06-28 03:58 UTCGHSA enrichment
  48. 2026-06-27 14:54 UTCGHSA enrichment
  49. 2026-06-27 03:08 UTCEPSS rescore
  50. 2026-06-27 01:50 UTCGHSA enrichment
  51. 2026-06-26 12:46 UTCGHSA enrichment
  52. 2026-06-25 23:42 UTCGHSA enrichment
  53. 2026-06-25 13:49 UTCEPSS rescore
  54. 2026-06-25 10:36 UTCGHSA enrichment
  55. 2026-06-24 21:31 UTCGHSA enrichment
  56. 2026-06-24 14:05 UTCEPSS rescore
  57. 2026-06-24 08:27 UTCGHSA enrichment
  58. 2026-06-23 21:33 UTCEPSS rescore
  59. 2026-06-23 21:33 UTCEPSS rescore
  60. 2026-06-23 19:22 UTCGHSA enrichment
  61. 2026-06-23 06:16 UTCGHSA enrichment
  62. 2026-06-22 17:02 UTCGHSA enrichment
  63. 2026-06-22 03:25 UTCGHSA enrichment
  64. 2026-06-21 12:45 UTCGHSA enrichment
  65. 2026-06-20 23:38 UTCGHSA enrichment
  66. 2026-06-20 10:31 UTCGHSA enrichment
  67. 2026-06-19 21:22 UTCGHSA enrichment
  68. 2026-06-19 08:17 UTCGHSA enrichment
  69. 2026-06-18 19:13 UTCGHSA enrichment
  70. 2026-06-18 06:03 UTCGHSA enrichment
  71. 2026-06-17 16:56 UTCGHSA enrichment
  72. 2026-06-17 03:51 UTCGHSA enrichment
  73. 2026-06-16 14:46 UTCEG score recompute
  74. 2026-06-16 14:46 UTCGHSA enrichment

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-54293?
CVE-2026-54293 is a high vulnerability published on June 16, 2026. NLTK (Natural Language Toolkit) is a suite of open source Python modules, data sets, and tutorials supporting research and development in Natural Language Processing. Prior to 3.10.0-rc1, nltk.data.load() in NLTK is vulnerable to path traversal via URL-encoded path separators and traversal segments…
When was CVE-2026-54293 disclosed?
CVE-2026-54293 was first published in the National Vulnerability Database on June 16, 2026, with the most recent update on July 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54293 actively exploited?
CVE-2026-54293 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 33.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-54293?
CVE-2026-54293 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-54293?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54293, 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-54293

Explore →

Is Your Infrastructure Affected by CVE-2026-54293?

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

Start Free Scan →Browse All CVEs