CVE-2026-78682

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (38th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated

Also known asEUVD-2026-65228 (ENISA EUVD) · GHSA-6ww7-3frv-cqxh (GitHub Security Advisories) · GHSA-crp9-r7rq-c8cg (GitHub Security Advisories) · PYSEC-2026-3733 (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.4%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

NLTK before 3.10.3 contains a server-side request forgery vulnerability in nltk.pathsec.urlopen (and callers nltk.data.load, nltk.downloader.Downloader.index/download) when an HTTP proxy is configured. pathsec.urlopen validates the requested hostname locally, but proxy-handler inheritance disables the safe HTTP/HTTPS handlers so the actual fetch is performed by the proxy against a destination that is never re-validated. An attacker can supply a validated public URL that the proxy forwards to an internal loopback-only service, allowing disclosure of internal HTTP resources, loading of forged downloader indexes, and installation of attacker-chosen package content.

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.4%
EPSS %ILE
38th
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.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-05). 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 25, 2026

Last Modified

October 12, 2026

Advisory Details (2)

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

NLTK before 3.10.3 SSRF Protection Bypass via Proxy | Advisories | VulnCheck

https://www.vulncheck.com/advisories/nltk-before-ssrf-protection-bypass-via-proxy
GitHub advisoryMentions a patch (unverified)

pathsec SSRF protection can be bypassed when a proxy is configured · Advisory · nltk/nltk · GitHub

https://github.com/nltk/nltk/security/advisories/GHSA-6ww7-3frv-cqxh

Patch Availability(5)

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
pipnltk @ 3.10.3 (fixes <= 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
nltk0.8 ... 3.9b1 (68 versions)
  • every version up to 3.10.3: fixed in 3.10.3
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 37× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 182 rows 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 82 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-78682?
CVE-2026-78682 is a high-severity vulnerability; its CVE record was published on August 25, 2026. NLTK before 3.10.3 contains a server-side request forgery vulnerability in nltk.pathsec.urlopen (and callers nltk.data.load, nltk.downloader.Downloader.index/download) when an HTTP proxy is configured. pathsec.urlopen validates the requested hostname locally, but proxy-handler inheritance disables…
When was CVE-2026-78682 made public?
CVE-2026-78682 was made public on August 11, 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 25, 2026. EchelonGraph's copy of the record carries a last-modified date of October 12, 2026; the record at its source may have been updated since.
Is CVE-2026-78682 actively exploited?
CVE-2026-78682 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (38th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-78682?
CVE-2026-78682 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-78682?
A fix for CVE-2026-78682 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-78682 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-78682

Explore →

Is Your Infrastructure Affected by CVE-2026-78682?

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