Hydra is a framework for elegantly configuring complex applications. From 1.3.4 until 1.3.6 and 1.4.0.dev9, the instantiate() target blacklist introduced for CVE-2026-68508 incompletely checks the effective callable selected by the target field. Execution wrappers such as timeit.timeit, executable deserialization through pickle.loads, aliases, callable-returning helpers, generic dispatch, and deferred calls can obscure or defer the effective target and bypass name-based authorization. An attacker who causes an application to instantiate untrusted Hydra configuration can use these gaps to execute code with the application's privileges. This issue is fixed in versions 1.3.6 and 1.4.0.dev9.
CVE-2026-106442
HIGHPre-NVD 7.87.8
EchelonGraph scoreLOW confidence
This high-severity CVE scores 7.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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: secondary
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 7.8Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 7.8
- EG Score
- 7.8HIGHlow confidence
- EG Risk
- 40EG Risk 40/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 computedSeverity78% × 45%Exploitation0% × 40%Automatability30% × 15%CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).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
- —
- EPSS %ILE
- —
- KEV
- Not listed
CISA SSVCTrack at low or medium mission impact; Track or 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 none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). 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
October 6, 2026
Last Modified
October 7, 2026
Advisory Details (6)
Auto-updated Oct 6, 2026Patch available. Sources: github, github_pr, github_commit, github_release.
github_release Patch Available
Hydra 1.3.6
Patch available: hydra-ecosystem/hydra v1.3.6
https://github.com/hydra-ecosystem/hydra/releases/tag/v1.3.6github_commit
commit f462811117b5 (hydra-ecosystem/hydra)
Fix landed in hydra-ecosystem/hydra commit f462811117b5 — awaiting tagged release
https://github.com/hydra-ecosystem/hydra/commit/f462811117b5ecfd2ed652ed52d6b4e3771bd943github_commit Patch Available
commit 2c82bbb3f396 (hydra-ecosystem/hydra)
Patch available: hydra-ecosystem/hydra v1.3.6 (contains commit 2c82bbb3f396)
https://github.com/hydra-ecosystem/hydra/commit/2c82bbb3f39603b336cb852461739fdf7a38798agithub_pr Patch Available
Backport instantiate target authorization hardening to 1.3
Patch available: hydra-ecosystem/hydra v1.3.6 (PR #3413 merged 2026-08-26)
https://github.com/hydra-ecosystem/hydra/pull/3413github_pr
Harden instantiate() target authorization
Fix merged in hydra-ecosystem/hydra PR #3412 on 2026-08-26 — awaiting tagged release
https://github.com/hydra-ecosystem/hydra/pull/3412githubMentions a patch (unverified)
Hydra instantiate target blacklist bypasses permit code execution · Advisory · hydra-ecosystem/hydra · GitHub
https://github.com/hydra-ecosystem/hydra/security/advisories/GHSA-rqx7-p7vv-w7hrVendor Advisories for CVE-2026-106442(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| hydra-core | 1.3.4, 1.3.5 |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 3× in last 7d / 3× 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.
- 2026-10-06 19:33 UTCEG score recompute
- 2026-10-06 19:03 UTCEG score recompute
- 2026-10-06 19:01 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(4)
What is CVE-2026-106442?
CVE-2026-106442 is a high vulnerability published on October 6, 2026. Hydra is a framework for elegantly configuring complex applications. From 1.3.4 until 1.3.6 and 1.4.0.dev9, the instantiate() target blacklist introduced for CVE-2026-68508 incompletely checks the effective callable selected by the target field. Execution wrappers such as timeit.timeit, executable…
When was CVE-2026-106442 disclosed?
CVE-2026-106442 was first published on October 6, 2026, with the most recent update on October 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-106442?
CVE-2026-106442 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-106442?
A fix for CVE-2026-106442 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-106442 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-106442
Is Your Infrastructure Affected by CVE-2026-106442?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.