Hydra is a framework for elegantly configuring complex applications. Prior to 1.3.6 and 1.4.0.dev9, Hydra passes Python logging configuration to logging.config.dictConfig() without applying Hydra's target policy to handler class values or formatter, filter, handler, queue, and listener factories. An attacker who controls Hydra logging configuration can therefore select an importable class or factory and cause it to be invoked with the application's privileges, even in versions where instantiate() is protected because the logging path does not use instantiate(). This issue is fixed in versions 1.3.6 and 1.4.0.dev9.
CVE-2026-106441
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).
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.8
- EG Score
- 7.8HIGHlow confidence
- EG Risk
- 35EG 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 computedSeverity78% × 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
- —
- EPSS %ILE
- —
- 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
October 6, 2026
Last Modified
October 7, 2026
Advisory Details (4)
Auto-updated Oct 6, 2026commit ff3e4dba890c (hydra-ecosystem/hydra)
Patch available: hydra-ecosystem/hydra v1.3.6 (contains commit ff3e4dba890c)
https://github.com/hydra-ecosystem/hydra/commit/ff3e4dba890c29a21d8c2bb867ee87d37ccf21d0commit 76bfc30ce1f3 (hydra-ecosystem/hydra)
Fix landed in hydra-ecosystem/hydra commit 76bfc30ce1f3 — awaiting tagged release
https://github.com/hydra-ecosystem/hydra/commit/76bfc30ce1f3105416941dd2e3a562568e369120Harden logging target resolution on 1.3
Patch available: hydra-ecosystem/hydra v1.3.6 (PR #3420 merged 2026-08-29)
https://github.com/hydra-ecosystem/hydra/pull/3420Hydra logging configuration permits unsafe callable resolution · Advisory · hydra-ecosystem/hydra · GitHub
https://github.com/hydra-ecosystem/hydra/security/advisories/GHSA-c3wx-c55w-pxjqVendor Advisories for CVE-2026-106441(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 | 0.1.4 ... 1.3.5 (50 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 5× in last 7d / 5× 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-07 19:21 UTCEG score recompute
- 2026-10-07 19:02 UTCEG score recompute
- 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 product + same CWE)
Frequently asked(4)
What is CVE-2026-106441?
When was CVE-2026-106441 disclosed?
What is the CVSS score of CVE-2026-106441?
How do I remediate CVE-2026-106441?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-106441
Is Your Infrastructure Affected by CVE-2026-106441?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.