CVE-2026-106441 · GHSA-c3wx-c55w-pxjq
Hydra logging configuration permits unsafe callable resolution
- Risk score
- 53/100
- CVSS
- 7.8 v3.1
- Exploit chance (30 days)
- 0.2%
- Published
- 6 Oct 2026
Open in the live forecast Today's forecast
What to know
- What it is
- 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 contr…
- Affected
- hydra-core (pip) < 1.3.6; hydra-core (pip) >= 1.4.0.dev0, < 1.4.0.dev9
- Fix
- Upgrade hydra-core to 1.3.6 or 1.4.0.dev9 (whichever matches your release line) or later.
- Exploitation
- No known exploitation
Story map
At a glance
hydra-core: Amber, patch this week. Hydra is a framework for elegantly configuring complex applications. From 1.3.4 until 1.3.7 and 1.4.0.dev10, Hydra stores legacy instantiate target blocklists and related execution-policy collections in mutable module-level state. An attacker who controls multiple sibling target entries can resolve hydra._internal.tar…
The flaws
- CVE-2026-106441: Hydra logging configuration permits unsafe callable resolution (CVSS 7.8 · EPSS 0%)
- CVE-2026-106439: Hydra: Mutable instantiate policy sets allow target blocklist bypass (CVSS 8.5 · EPSS 0%)
- CVE-2026-106442: Hydra instantiate target blacklist bypasses permit code execution (CVSS 7.8 · EPSS 0%)
The fix
Upgrade hydra-core: 1.3.6 · 1.4.0 · 1.3.7 or later on your release line
Who is exposed: hydra-core (pip) >= 1.3.4, < 1.3.7; hydra-core (pip) >= 1.4.0.dev4, < 1.4.0.dev10
Where it stands
- No known exploitation
Connects to
- Same weakness: Code injection (CWE-94). 239 other warnings in 30 days
Why it is Yellow
- CVSS 7.8 high
- On your watchlist: PyPI
Affected packages
| Package | Ecosystem | Vulnerable | Fixed in |
|---|---|---|---|
| hydra-core | pip | < 1.3.6 | 1.3.6 |
| hydra-core | pip | >= 1.4.0.dev0, < 1.4.0.dev9 | 1.4.0.dev9 |
References
- https://github.com/advisories/GHSA-c3wx-c55w-pxjq
- https://github.com/hydra-ecosystem/hydra/security/advisories/GHSA-c3wx-c55w-pxjq
- https://nvd.nist.gov/vuln/detail/CVE-2026-106441
- https://github.com/hydra-ecosystem/hydra/pull/3420
- https://github.com/hydra-ecosystem/hydra/commit/76bfc30ce1f3105416941dd2e3a562568e369120
- https://github.com/hydra-ecosystem/hydra/commit/ff3e4dba890c29a21d8c2bb867ee87d37ccf21d0
- https://github.com/hydra-ecosystem/hydra/releases/tag/v1.3.6
- https://github.com/advisories/GHSA-c3wx-c55w-pxjq
Original description
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.
Last activity 6 Oct 2026. Patch Forecast updates every hour.