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-09-08. 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 — 5 sources updated this weekElevated

Also known asEUVD-2026-64338 (ENISA EUVD) · GHSA-f833-7jw8-xwrv (GitHub Security Advisories) · GHSA-qq3h-cgj8-w3fx (GitHub Security Advisories) · PYSEC-2026-3789 (OSV.dev)Source: ENISA EUVD

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 impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
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
51st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

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.

The score's inputs: 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

October 14, 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

Patch Availability(6)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-trustyai-nemo-guardrails-server-rhel9:17915666312026-10-21redhat
redhatrhoai/odh-workbench-jupyter-pytorch-llmcompressor-cuda-py312-rhel9:17918671892026-10-21redhat
redhatrhoai/odh-trustyai-nemo-guardrails-server-rhel9:17915561282026-10-19redhat
redhatrhoai/odh-llama-stack-core-rhel9:17891212862026-09-30redhat
redhatrhoai/odh-ta-lmes-job-rhel9:17889358632026-09-21redhat
pipnltk @ 3.10.2 (fixes >= 3.10.0, < 3.10.2)—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

(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(2)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 64× 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 172 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 72 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

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 October 14, 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 (51st 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.