CVE-2026-106442: Hydra instantiate target blacklist bypasses permit code execution
Summary Hydra's instantiate() API resolves and invokes Python callables named by the target field in configuration. The target blacklist introduced for CVE-2026-68508 was incomplete. Representative bypasses included execution wrappers such as timeit.timeit, executable deserialization through pickle.loads, and generic dispatch or wrapper targets that obscured the effective callable.
Published Oct 7, 2026
Affected packages
hydra-core
- Ecosystem
- PyPI
- Affected
- >= 1.3.4, < 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's instantiate() API resolves and invokes Python callables named by the _target_ field in configuration. The target blacklist introduced for CVE-2026-68508 was incomplete.
Representative bypasses included execution wrappers such as timeit.timeit, executable deserialization through pickle.loads, and generic dispatch or wrapper targets that obscured the effective callable. Target aliases, callable-returning helpers, and deferred dispatch could similarly bypass name-based checks.
An attacker who can cause an application to instantiate an untrusted Hydra configuration can use these gaps to execute code with the application's privileges.
Fix
Hydra 1.3.6 expands and hardens the blacklist used by the 1.3 compatibility line. It blocks the reported execution and deserialization surfaces, checks canonical callable identities and aliases, mediates callable results, and blocks generic dispatch and wrapper targets that bypass immediate target checks.
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 configuration safe to instantiate.
Hydra 1.4.0.dev9 applies the same hardening and introduces the execution whitelist as the recommended primary security boundary. When a whitelist is supplied, targets are rejected unless trusted Python code authorizes them. If no whitelist is supplied, Hydra preserves legacy behavior with a deprecation warning and the blacklist as a best-effort compatibility fallback. Targets that permit configuration to select or supply executable behavior remain non-whitelistable.
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 instantiate configuration from untrusted sources. On Hydra 1.4 and later, constrain untrusted configuration with a narrow execution whitelist supplied by trusted Python code.
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-rqx7-p7vv-w7hr
- https://nvd.nist.gov/vuln/detail/CVE-2026-106442
- https://github.com/hydra-ecosystem/hydra/pull/3412
- https://github.com/hydra-ecosystem/hydra/pull/3413
- https://github.com/hydra-ecosystem/hydra/commit/2c82bbb3f39603b336cb852461739fdf7a38798a
- https://github.com/hydra-ecosystem/hydra/commit/f462811117b5ecfd2ed652ed52d6b4e3771bd943
- https://github.com/hydra-ecosystem/hydra/releases/tag/v1.3.6
- https://github.com/advisories/GHSA-rqx7-p7vv-w7hr
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-106441
Hydra logging configuration permits unsafe callable resolution
high7.8Oct 7, 2026CVE-2026-68508
Hydra: hydra.utils.instantiate with untrusted config can lead to code execution
high7.8Aug 21, 2026
