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
Trending — 3 sources updated this weekElevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: Elevated riskExposed: 0

A fix is available — apply it.

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)
EG Risk
65(Attend)
EG Risk 65/100SSVC: Attend

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
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
1%
EPSS %ILE
44%
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(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhoai/odh-llama-stack-core-rhel9:17837015982026-07-21redhat
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

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
nltk3.10.0-1 ... 3.9.3-1 (12 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
nltk3.10.0-1 ... 3.9.3-1 (8 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
nltk3.10.0-1, 3.10.1-1, 3.9.1-2, 3.9.2-1, 3.9.3-1——
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 23× in last 7d / 92× 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.

Showing the most recent 100 of 191 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + 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 1% probability of exploitation in the next 30 days, which ranks it in the top 56.0% of all scored CVEs.
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