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
“—” beside the score: it is equal to the CVSS score beside it.
Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-10-07. A secondary CVSS source baseline 7.8; sources differ by 0.0.
Also known asEUVD-2026-93664 (ENISA EUVD) · GHSA-c3wx-c55w-pxjq (GitHub Security Advisories)Source: ENISA EUVD
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.8
- EG Score
- 7.8HIGHhigh confidence
- EG Risk
- 35EG Risk 35/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)Severity78% × 45%Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.2% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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. - EPSS PROB
- 0.2%
- EPSS %ILE
- 5th
- 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.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.
- EG Severity
- 7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade 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; 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). 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; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (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
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(5)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2026:92452Red Hat Product SecurityCritical
Red Hat Security Advisory: Red Hat Enterprise Linux AI 3.5.2 enhancement update
- RHSA-2026:92449Red Hat Product SecurityCritical
Red Hat Security Advisory: Red Hat Enterprise Linux AI 3.5.2 enhancement update
- RHSA-2026:82415Red Hat Product SecurityCritical
Red Hat Security Advisory: Red Hat AI Inference 3.5.2 (cpu)
- RHSA-2026:82368Red Hat Product SecurityCritical
Red Hat Security Advisory: Red Hat AI Inference 3.5.2 (cuda)
- GHSA-c3wx-c55w-pxjqGitHub Security AdvisoriesHigh
Hydra logging configuration permits unsafe callable resolution
Patch Availability(4)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| redhat | rhaii/vllm-cuda-rhel9:1791473631 | 2026-10-13 | redhat |
| redhat | rhaii/vllm-cpu-rhel9:1791473614 | 2026-10-13 | redhat |
| pip | hydra-core @ 1.3.6 (fixes < 1.3.6) | — | ghsa |
| pip | hydra-core @ 1.4.0.dev9 (fixes >= 1.4.0.dev0, < 1.4.0.dev9) | — | 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
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| hydra-core | 1.4.0.dev1 ... 1.4.0.dev8 (6 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 46× 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 it from the CNA feed. 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). Most recent first.
- 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
- 2026-11-01 08:00 UTCGHSA enrichmentGHSA-c3wx-c55w-pxjq · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-11-01 08:00 UTCEG score recompute
- 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.2% · 5th percentile
- 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
- 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.2% · 5th percentile
- 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.2% · 5th percentile
- 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.2% · 5th percentile
- 2026-10-27 11:16 UTCEG score recompute
- 2026-10-27 11:16 UTCVendor advisory
- 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.2% · 5th percentile
- 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.2% · 5th percentile
- 2026-10-25 14:54 UTCEG score recompute
- 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.2% · 5th percentile
- 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.2% · 5th percentile
- 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
- 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.2% · 5th percentile
- 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.2% · 5th percentile
- 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.2% · 5th percentile
- 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.2% · 5th percentile
- 2026-10-18 05:08 UTCEG score recompute
- 2026-10-17 19:24 UTCEG score recompute
- 2026-10-17 19:24 UTCVendor advisory
- 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
- 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.2% · 5th percentile
Show 21 moreShow fewer
- 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.2% · 5th percentile
- 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.2% · 5th percentile
- 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
- 2026-10-12 16:39 UTCEG score recompute
- 2026-10-11 20:14 UTCEG score recompute
- 2026-10-11 18:27 UTCEG score recompute
- 2026-10-11 15:00 UTCEG score recompute
- 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.2% · 5th percentile
- 2026-10-10 20:13 UTCEG score recompute
- 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.2% · 5th percentile
- 2026-10-10 08:05 UTCEG score recompute
- 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.2% · 5th percentile
- 2026-10-08 19:38 UTCEG score recompute
- 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.2% · 5th percentile
- 2026-10-08 07:29 UTCEG score recompute
- 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.2% · 5th percentile
- 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 recomputeFirst assessed: 7.8 HIGH
- 2026-10-06 19:01 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same vendor + same CWE)
Same product
3 shownPyPI:hydra-core
Same vendor
10 shownredhat:RHSA-2026:82368
Frequently asked(5)
What is CVE-2026-106441?
When was the CVE record for CVE-2026-106441 published?
Is CVE-2026-106441 actively exploited?
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.