CVE-2026-106442 · GHSA-rqx7-p7vv-w7hr
Hydra instantiate target blacklist bypasses permit code execution
- 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. From 1.3.4 until 1.3.6 and 1.4.0.dev9, the instantiate() target blacklist introduced for CVE-2026-68508 incompletely checks the effective callable selected by the target field. Execution wrappers such as timeit.timeit, executable deserialization thro…
- Affected
- hydra-core (pip) >= 1.3.4, < 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-106442: Hydra instantiate target blacklist bypasses permit code execution (CVSS 7.8 · EPSS 0%)
- CVE-2026-106439: Hydra: Mutable instantiate policy sets allow target blocklist bypass (CVSS 8.5 · EPSS 0%)
- CVE-2026-106441: Hydra logging configuration permits unsafe callable resolution (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: CWE-184 (CWE-184). 31 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.4, < 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-rqx7-p7vv-w7hr
- 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
Original description
Hydra is a framework for elegantly configuring complex applications. From 1.3.4 until 1.3.6 and 1.4.0.dev9, the instantiate() target blacklist introduced for CVE-2026-68508 incompletely checks the effective callable selected by the target field. Execution wrappers such as timeit.timeit, executable deserialization through pickle.loads, aliases, callable-returning helpers, generic dispatch, and deferred calls can obscure or defer the effective target and bypass name-based authorization. An attacker who causes an application to instantiate untrusted Hydra configuration can use these gaps to execute code with the application's privileges. This issue is fixed in versions 1.3.6 and 1.4.0.dev9.
Last activity 6 Oct 2026. Patch Forecast updates every hour.