CVE-2026-62384

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated
7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

NLTK versions before 3.10.2 contain a symlink-based sandbox bypass in FramenetCorpusReader that allows attackers to read arbitrary XML files outside the corpus root. Attackers can place symlinks with names containing no path separators inside the corpus subdirectory, which pass the path validation guard and are resolved to files outside the intended corpus root when accessed via frame_by_name(), _lu_file(), or doc() methods.

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 (value × EchelonGraph’s weight)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.7%
EPSS %ILE
49th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

Advisory Details (2)

Auto-updated Aug 22, 2026
Patch available. Sources: github.
Web page

NLTK FramenetCorpusReader Symlink Sandbox Bypass before 3.10.2 | Advisories | VulnCheck

https://www.vulncheck.com/advisories/nltk-framenetcorpusreader-symlink-sandbox-bypass-before
GitHub advisoryMentions a patch (unverified)

Symlink-based sandbox bypass in FramenetCorpusReader (bypasses the fix for CVE-2026-54292) · Advisory · nltk/nltk · GitHub

https://github.com/nltk/nltk/security/advisories/GHSA-f833-7jw8-xwrv

Vendor Advisories for CVE-2026-62384(3)

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 / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-llama-stack-core-rhel9:17891212862026-09-30redhat
redhatrhoai/odh-ta-lmes-job-rhel9:17889358632026-09-21redhat

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

(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.0 up to 3.10.2: fixed in 3.10.2
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 19× in last 7d / 78× 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.

Showing the most recent 100 of 142 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 42 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-62384?
CVE-2026-62384 is a high-severity vulnerability; its CVE record was published on August 22, 2026. NLTK versions before 3.10.2 contain a symlink-based sandbox bypass in FramenetCorpusReader that allows attackers to read arbitrary XML files outside the corpus root. Attackers can place symlinks with names containing no path separators inside the corpus subdirectory, which pass the path validation…
When was CVE-2026-62384 made public?
CVE-2026-62384 was made public on August 7, 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-62384 actively exploited?
CVE-2026-62384 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (49th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-62384?
CVE-2026-62384 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-62384?
A fix for CVE-2026-62384 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-62384 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-62384

Explore →

Is Your Infrastructure Affected by CVE-2026-62384?

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

Book a Demo →Browse All CVEs