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.3%, top 84% of all CVEs by exploit prediction. 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%CVSS: 7.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.8(medium)
EG Risk
35(Track)
EG Risk 35/100SSVC: Track

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%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
16%
KEV
Not listed

Published

August 21, 2026

Last Modified

August 21, 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
github Patch Available

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

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

Weakness Classification(2)

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

Data Freshness Timeline

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

  1. 2026-08-25 23:10 UTCEG score recompute
  2. 2026-08-25 13:49 UTCEPSS rescore
  3. 2026-08-24 22:46 UTCEG score recompute
  4. 2026-08-24 10:43 UTCEG score recompute
  5. 2026-08-23 10:35 UTCEG score recompute
  6. 2026-08-23 00:19 UTCEPSS rescore
  7. 2026-08-21 22:25 UTCEG score recompute
  8. 2026-08-21 21:51 UTCEG score recompute
  9. 2026-08-21 21:24 UTCEG score recompute
  10. 2026-08-21 20:19 UTCEG score recompute
  11. 2026-08-21 20:19 UTCMITRE cvelistV5first tracked

Related CVEs(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 in the National Vulnerability Database on August 21, 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% probability of exploitation in the next 30 days, which ranks it in the top 83.6% of all scored CVEs.
What is the CVSS score of CVE-2026-68508?
CVE-2026-68508 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-68508?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68508, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for 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.

Start Free Scan →Browse All CVEs