CVE-2026-106441: Hydra logging configuration permits unsafe callable resolution
Summary Hydra passed its Python logging configuration to logging.config.dictConfig(). Python's logging configurator can resolve and invoke importable classes and factories named by configuration, including handler class values and formatter, filter, handler, queue, and listener () factories. This logging path was not mediated by Hydra's target policy.
Published Oct 7, 2026
Affected packages
hydra-core
- Ecosystem
- PyPI
- Affected
- < 1.3.6
- Fixed in
- 1.3.6
- Check
pip show hydra-core
hydra-core
- Ecosystem
- PyPI
- Affected
- >= 1.4.0.dev0, < 1.4.0.dev9
- Fixed in
- 1.4.0.dev9
- Check
pip show hydra-core
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
Hydra passed its Python logging configuration to logging.config.dictConfig(). Python's logging configurator can resolve and invoke importable classes and factories named by configuration, including handler class values and formatter, filter, handler, queue, and listener () factories.
This logging path was not mediated by Hydra's target policy. In versions that already protected instantiate(), logging resolution bypassed those controls because it did not use instantiate().
An attacker who can control a Hydra logging configuration can use a custom class or factory to execute code with the application's privileges when Hydra configures logging.
Fix
Hydra now applies its target policy to callable resolution and invocation in Hydra-configured Python logging. It authorizes custom factories, handlers, formatters, filters, queues, listeners, aliases, discovery results, and callable results before they can be used.
Hydra 1.3.6 uses the hardened blacklist. The Hydra 1.3 blacklist is a best-effort, defense-in-depth measure. It is not a complete security boundary and does not make untrusted logging configuration safe.
Hydra 1.4.0.dev9 introduces the execution whitelist as the recommended primary boundary, with the blacklist retained as a deprecated compatibility fallback. When an execution whitelist is supplied, Hydra automatically permits targets used by its built-in logging configurations, while custom logging integrations must be explicitly authorized by trusted Python code. If no whitelist is supplied, Hydra warns and preserves legacy fallback behavior.
Remediation
Upgrade to Hydra 1.3.6, or to Hydra 1.4.0.dev9 or later when testing the 1.4 prerelease line.
On Hydra 1.3, do not compose logging configuration from untrusted sources. On Hydra 1.4 and later, constrain custom logging targets with a narrow execution whitelist supplied by trusted Python code. The execution whitelist controls callable selection; it is not general validation of all logging settings.
For Hydra 1.4 execution-whitelist configuration, see:
https://hydra.cc/docs/advanced/execution_whitelist/
Credited to hash3liZer, eros938.
References
- 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
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More PyPI vulnerabilities
All PyPI entriesGHSA-wf6j-7hvr-gr93
Hydra legacy target blacklist permits unsafe PyYAML loading
high7.8Oct 27, 2026CVE-2026-106439
Hydra: Mutable instantiate policy sets allow target blocklist bypass
high8.5Oct 7, 2026CVE-2026-106442
Hydra instantiate target blacklist bypasses permit code execution
high7.8Oct 7, 2026CVE-2026-68508
Hydra: hydra.utils.instantiate with untrusted config can lead to code execution
high7.8Aug 21, 2026
