https://db.gcve.eu/rss/recent/all/10 Most recent entries from all 2026-10-08T16:00:10.144336+00:00 Vulnerability-Lookup info@gcve.eu python-feedgen Contains only the most 10 recent entries. https://db.gcve.eu/vuln/fkie_cve-2026-106439 fkie_cve-2026-106439 2026-10-08T16:00:10.164506+00:00

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.target_policy.UNCONTROLLED_EXECUTION_TARGETS.discard through instantiate(), remove a denied target, and then invoke that target because sibling nodes are processed in insertion order against the same modified policy. The mutation persists in process-global state and can enable code execution with the application's privileges, while a narrow execution whitelist supplied by trusted Python code is not bypassed by the reported direct mutation path. This issue is fixed in versions 1.3.7 and 1.4.0.dev10.

 https://db.gcve.eu/vuln/ghsa-mwj6-rfh8-7qf4 GHSA-mwj6-rfh8-7qf4 — Hydra: Mutable instantiate policy sets allow target blocklist bypass 2026-10-08T16:00:10.164574+00:00

Affected: PyPI: hydra-core

## Summary

Hydra's legacy `instantiate()` target blocklists and related execution-policy collections are stored in mutable module-level state. Because `_locate()` can resolve attributes on imported objects, a configuration can resolve a mutation method such as `.discard()`, modify the active policy, and then instantiate a target that would otherwise be blocked.

## Impact

A configuration controlling multiple sibling `_target_` entries can first remove an entry from a target blocklist and then invoke the removed target. Sibling nodes are processed in insertion order and consult the same mutable module-level policy.

This affects the legacy/default path without an execution whitelist. The 1.3 blocklist is a defense-in-depth measure rather than a complete security boundary, and applications must not treat arbitrary untrusted configuration as safe to instantiate or use for Python logging configuration.

Released `hydra-core` versions 1.3.4 through 1.3.6 and 1.4.0.dev4 through 1.4.0.dev9 are affected. Fixed releases are 1.3.7 and 1.4.0.dev10. The reported direct mutation path does not bypass an execution whitelist restricted to intended application targets and supplied by trusted Python code. During remediation, Hydra additionally hardened generic discovery, dispatch, introspection, alias, callable-result, and deferred-callable paths that could otherwise undermine name-only authorization.

## Technical details

In `hydra-core` 1.3.4 and 1.3.5, the mutable blocklist is reachable…