Hydra: Mutable instantiate policy sets allow target blocklist bypass
## 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 as: `hy
- Products
- hydra-core
- Affected versions
- 1.3.4, 1.3.5, 1.3.6, 1.4.0.dev4, 1.4.0.dev5, 1.4.0.dev6, 1.4.0.dev8, 1.4.0.dev9
- Fixed versions
- 1.3.7, 1.4.0.dev10
- CVEs
- CVE-2026-106439
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 30 Oct 2026, 18:13 UTC · Revision 1
Source evidence
Hydra: Mutable instantiate policy sets allow target blocklist bypass
core-osv · Original sourcePublished 15 Oct 2026, 10:22 UTC
## 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 as: `hy
osv:PYSEC-2026-4222
hydra-core
Fixed versions: 1.3.7, 1.4.0.dev10
Complete source record
{
"id": "5a7f4e509e08085e0a6b4be389772558057ae018097f3f966161a54a80be6245",
"url": "https://osv.dev/vulnerability/PYSEC-2026-4222",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Hydra: Mutable instantiate policy sets allow target blocklist bypass",
"summary": "## 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 as: `hy",
"evidence": "osv:PYSEC-2026-4222",
"products": [
{
"name": {
"value": "hydra-core",
"evidence": "/affected/0/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "1.3.7",
"evidence": "/affected/0/ranges"
},
{
"value": "1.4.0.dev10",
"evidence": "/affected/0/ranges"
}
],
"affected_versions": [
{
"value": "1.3.4",
"evidence": "/affected/0/versions"
},
{
"value": "1.3.5",
"evidence": "/affected/0/versions"
},
{
"value": "1.3.6",
"evidence": "/affected/0/versions"
},
{
"value": "1.4.0.dev4",
"evidence": "/affected/0/versions"
},
{
"value": "1.4.0.dev5",
"evidence": "/affected/0/versions"
},
{
"value": "1.4.0.dev6",
"evidence": "/affected/0/versions"
},
{
"value": "1.4.0.dev8",
"evidence": "/affected/0/versions"
},
{
"value": "1.4.0.dev9",
"evidence": "/affected/0/versions"
}
]
}
],
"severity": "high",
"structured": {
"id": "PYSEC-2026-4222",
"aliases": [
"CVE-2026-106439",
"GHSA-mwj6-rfh8-7qf4",
"PYSEC-2026-4222"
],
"metrics": [
{
"type": "CVSS_V4",
"score": "CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N"
}
],
"affected": [
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "1.3.4"
},
{
"fixed": "1.3.7"
},
{
"introduced": "1.4.0.dev4"
},
{
"fixed": "1.4.0.dev10"
}
]
}
],
"package": {
"name": "hydra-core",
"purl": "pkg:pypi/hydra-core",
"ecosystem": "PyPI"
},
"versions": [
"1.3.4",
"1.3.5",
"1.3.6",
"1.4.0.dev4",
"1.4.0.dev5",
"1.4.0.dev6",
"1.4.0.dev8",
"1.4.0.dev9"
],
"database_specific": {
"source": "https://github.com/pypa/advisory-database/blob/main/vulns/hydra-core/PYSEC-2026-4222.yaml"
}
}
],
"modified": "2026-10-15T14:45:07.445702695Z",
"provider": "osv",
"references": [
"https://github.com/hydra-ecosystem/hydra/security/advisories/GHSA-mwj6-rfh8-7qf4",
"https://nvd.nist.gov/vuln/detail/CVE-2026-106439",
"https://github.com/hydra-ecosystem/hydra/commit/0dd18084589a3d3e577d1f1a8a48fb485c94a5e6",
"https://github.com/hydra-ecosystem/hydra/commit/4720dfca2bde27fa140ec287a05709668fbdf168",
"https://github.com/hydra-ecosystem/hydra",
"https://github.com/hydra-ecosystem/hydra/releases/tag/v1.3.7",
"https://pypi.org/project/hydra-core",
"https://github.com/advisories/GHSA-mwj6-rfh8-7qf4"
]
},
"related_cves": [
{
"value": "CVE-2026-106439",
"evidence": "/aliases"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 332643,
"published_at": "2026-10-15T10:22:48.376932+00:00"
}