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.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 7.5Exploit: Elevated riskExposed services: Not assessed

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.5HIGHmedium confidence
EG Risk
65
EG Risk 65/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
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
EPSS PROB
0.6%
EPSS %ILE
48th
KEV
Not listed

Published

June 16, 2026

Last Modified

September 9, 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(4)

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

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-ta-lmes-job-rhel9:17873309032026-09-08redhat
redhatrhoai/odh-trustyai-nemo-guardrails-server-rhel9:17873305852026-08-27redhat
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 rangeFix by version rangeDependents
nltk3.10.0-1 ... 3.9.3-1 (12 versions)
  • every version on: no fix on record
—
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.9.1-2, 3.9.2-1, 3.9.3-1
  • every version up to 3.10.0-1: fixed in 3.10.0-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
nltk0.8 ... 3.9b1 (65 versions)
  • every version up to 3.10.0: fixed in 3.10.0
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 29× 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 245 total refreshes for this CVE.

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

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 on June 16, 2026, with the most recent update on September 9, 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 0.6% probability of exploitation in the next 30 days (48th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-54293?
CVE-2026-54293 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-54293?
A fix for CVE-2026-54293 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-54293 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-54293

Explore →

Is Your Infrastructure Affected by CVE-2026-54293?

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

Book a Demo →Browse All CVEs