CVE-2026-68508

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (37th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Hydra is a framework for elegantly configuring complex applications. Prior to 1.3.4, hydra.utils.instantiate() resolves and calls Python objects selected by configuration through _resolve_target() in hydra/_internal/instantiate/_instantiate2.py, allowing attacker-controlled target values and arguments to choose dangerous callables. A consuming application, library, CLI workflow, or model loader that passes untrusted configuration, CLI overrides, or model metadata into hydra.utils.instantiate() can therefore execute arbitrary code in its own process, including reading or modifying files and credentials or terminating the process. Version 1.3.4 adds target blocking with an explicit HYDRA_INSTANTIATE_ALLOWLIST_OVERRIDE escape hatch. This issue is fixed in version 1.3.4.

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100CISA SSVC

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
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
37th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 21, 2026

Last Modified

September 9, 2026

Advisory Details (5)

Auto-updated Aug 21, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
github_release Patch Available

Hydra 1.3.4

Patch available: hydra-ecosystem/hydra v1.3.4

https://github.com/hydra-ecosystem/hydra/releases/tag/v1.3.4
github_commit Patch Available

commit 7faad0dcedfb (hydra-ecosystem/hydra)

Patch available: hydra-ecosystem/hydra v1.3.4 (contains commit 7faad0dcedfb)

https://github.com/hydra-ecosystem/hydra/commit/7faad0dcedfb4c0a364aa1067c0080fd6fdf8dca
github_pr Patch Available

Harden instantiate target blocklist

Patch available: hydra-ecosystem/hydra v1.3.4 (PR #3261 merged 2026-07-04)

https://github.com/hydra-ecosystem/hydra/pull/3261
generic

Harden instantiate blocklist for 1.3.x · Issue #3259 · hydra-ecosystem/hydra · GitHub

https://github.com/hydra-ecosystem/hydra/issues/3259
githubMentions a patch (unverified)

hydra.utils.instantiate with untrusted config can lead to code execution · Advisory · hydra-ecosystem/hydra · GitHub

https://github.com/hydra-ecosystem/hydra/security/advisories/GHSA-2cp2-2r3c-7p7r

Vendor Advisories for CVE-2026-68508(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
redhatrhaii/vllm-cpu-rhel9:17900757932026-09-23redhat
redhatrhaii/vllm-cuda-rhel9:17900901312026-09-23redhat

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

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
hydra-core0.1.4 ... 1.3.3 (48 versions)
  • every version up to 1.3.4: fixed in 1.3.4
—

Weakness Classification(2)

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

Data Freshness Timeline

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

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

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

Frequently asked(5)

What is CVE-2026-68508?
CVE-2026-68508 is a high vulnerability published on August 21, 2026. Hydra is a framework for elegantly configuring complex applications. Prior to 1.3.4, hydra.utils.instantiate() resolves and calls Python objects selected by configuration through resolvetarget() in hydra/internal/instantiate/instantiate2.py, allowing attacker-controlled target values and arguments…
When was CVE-2026-68508 disclosed?
CVE-2026-68508 was first published on August 21, 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-68508 actively exploited?
CVE-2026-68508 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (37th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-68508?
CVE-2026-68508 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-68508?
A fix for CVE-2026-68508 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-68508 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-68508

Explore →

Is Your Infrastructure Affected by CVE-2026-68508?

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

Book a Demo →Browse All CVEs