{"items":[{"id":"NVI-00011792","kind":"vulnerability","title":"Hydra: Mutable instantiate policy sets allow target blocklist bypass","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-mwj6-rfh8-7qf4","CVE-2026-106439"],"plain_summary":"GitHub lists this reviewed advisory for hydra-core, hydra-core. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-3108496e522a202f1292d9aa45bb9196"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.457%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.39655. Missing scores are unknown.","source_id":"sr-3108496e522a202f1292d9aa45bb9196"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-2e382fe46c80b2c59f6c4ef66dadc00c","url":"https://github.com/advisories/GHSA-mwj6-rfh8-7qf4","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-mwj6-rfh8-7qf4","publisher":"GitHub Advisory Database","observed_at":"2026-11-01T00:58:46.232Z"},{"id":"sr-3108496e522a202f1292d9aa45bb9196","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-106439","publisher":"FIRST EPSS","observed_at":"2026-11-01T01:39:43.064Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-2e382fe46c80b2c59f6c4ef66dadc00c"],"technology":"hydra-core","known_exclusions":[],"conditions_summary":"## Summary\n\nHydra's legacy `instantiate()` target blocklists and related execution-policy\ncollections are stored in mutable module-level state. Because `_locate()` can\nresolve attributes on imported objects, a configuration can resolve a mutation\nmethod such as `.discard()`, modify the active policy, and then instantiate a\ntarget that would otherwise be blocked.\n\n## Impact\n\nA configuration controlling multiple sibling `_target_` entries can first\nremove an entry from a target blocklist and then invoke the removed target.\nSibling nodes are processed in insertion order and consult the same mutable\nmodule-level policy.\n\nThis affects the legacy/default path without an execution whitelist. The 1.3\nblocklist is a defense-in-depth measure rather than a complete security\nboundary, and applications must not treat arbitrary untrusted configuration as\nsafe to instantiate or use for Python logging configuration.\n\nReleased `hydra-core` versions 1.3.4 through 1.3.6 and 1.4.0.dev4 through\n1.4.0.dev9 are affected. Fixed releases are 1.3.7 and 1.4.0.dev10.\nThe reported direct mutation path does not bypass an execution whitelist\nrestricted to intended application targets and supplied by trusted Pyth","public_affected_ranges":[">= 1.3.4, < 1.3.7"]},{"certainty":"source_listed","source_ids":["sr-2e382fe46c80b2c59f6c4ef66dadc00c"],"technology":"hydra-core","known_exclusions":[],"conditions_summary":"## Summary\n\nHydra's legacy `instantiate()` target blocklists and related execution-policy\ncollections are stored in mutable module-level state. Because `_locate()` can\nresolve attributes on imported objects, a configuration can resolve a mutation\nmethod such as `.discard()`, modify the active policy, and then instantiate a\ntarget that would otherwise be blocked.\n\n## Impact\n\nA configuration controlling multiple sibling `_target_` entries can first\nremove an entry from a target blocklist and then invoke the removed target.\nSibling nodes are processed in insertion order and consult the same mutable\nmodule-level policy.\n\nThis affects the legacy/default path without an execution whitelist. The 1.3\nblocklist is a defense-in-depth measure rather than a complete security\nboundary, and applications must not treat arbitrary untrusted configuration as\nsafe to instantiate or use for Python logging configuration.\n\nReleased `hydra-core` versions 1.3.4 through 1.3.6 and 1.4.0.dev4 through\n1.4.0.dev9 are affected. Fixed releases are 1.3.7 and 1.4.0.dev10.\nThe reported direct mutation path does not bypass an execution whitelist\nrestricted to intended application targets and supplied by trusted Pyth","public_affected_ranges":[">= 1.4.0.dev4, < 1.4.0.dev10"]}],"null_published_at":"2026-11-01T14:34:14.108Z","source_updated_at":"2026-10-07T20:23:59.000Z","source_disclosed_at":"2026-10-07T20:23:57.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-11-01T00:58:46.232Z"},{"id":"NVI-00011792","kind":"vulnerability","title":"Hydra: Mutable instantiate policy sets allow target blocklist bypass","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-mwj6-rfh8-7qf4","CVE-2026-106439"],"plain_summary":"GitHub lists this reviewed advisory for hydra-core, hydra-core. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-2e382fe46c80b2c59f6c4ef66dadc00c"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-2e382fe46c80b2c59f6c4ef66dadc00c","url":"https://github.com/advisories/GHSA-mwj6-rfh8-7qf4","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-mwj6-rfh8-7qf4","publisher":"GitHub Advisory Database","observed_at":"2026-11-01T00:58:46.232Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-2e382fe46c80b2c59f6c4ef66dadc00c"],"technology":"hydra-core","known_exclusions":[],"conditions_summary":"## Summary\n\nHydra's legacy `instantiate()` target blocklists and related execution-policy\ncollections are stored in mutable module-level state. Because `_locate()` can\nresolve attributes on imported objects, a configuration can resolve a mutation\nmethod such as `.discard()`, modify the active policy, and then instantiate a\ntarget that would otherwise be blocked.\n\n## Impact\n\nA configuration controlling multiple sibling `_target_` entries can first\nremove an entry from a target blocklist and then invoke the removed target.\nSibling nodes are processed in insertion order and consult the same mutable\nmodule-level policy.\n\nThis affects the legacy/default path without an execution whitelist. The 1.3\nblocklist is a defense-in-depth measure rather than a complete security\nboundary, and applications must not treat arbitrary untrusted configuration as\nsafe to instantiate or use for Python logging configuration.\n\nReleased `hydra-core` versions 1.3.4 through 1.3.6 and 1.4.0.dev4 through\n1.4.0.dev9 are affected. Fixed releases are 1.3.7 and 1.4.0.dev10.\nThe reported direct mutation path does not bypass an execution whitelist\nrestricted to intended application targets and supplied by trusted Pyth","public_affected_ranges":[">= 1.3.4, < 1.3.7"]},{"certainty":"source_listed","source_ids":["sr-2e382fe46c80b2c59f6c4ef66dadc00c"],"technology":"hydra-core","known_exclusions":[],"conditions_summary":"## Summary\n\nHydra's legacy `instantiate()` target blocklists and related execution-policy\ncollections are stored in mutable module-level state. Because `_locate()` can\nresolve attributes on imported objects, a configuration can resolve a mutation\nmethod such as `.discard()`, modify the active policy, and then instantiate a\ntarget that would otherwise be blocked.\n\n## Impact\n\nA configuration controlling multiple sibling `_target_` entries can first\nremove an entry from a target blocklist and then invoke the removed target.\nSibling nodes are processed in insertion order and consult the same mutable\nmodule-level policy.\n\nThis affects the legacy/default path without an execution whitelist. The 1.3\nblocklist is a defense-in-depth measure rather than a complete security\nboundary, and applications must not treat arbitrary untrusted configuration as\nsafe to instantiate or use for Python logging configuration.\n\nReleased `hydra-core` versions 1.3.4 through 1.3.6 and 1.4.0.dev4 through\n1.4.0.dev9 are affected. Fixed releases are 1.3.7 and 1.4.0.dev10.\nThe reported direct mutation path does not bypass an execution whitelist\nrestricted to intended application targets and supplied by trusted Pyth","public_affected_ranges":[">= 1.4.0.dev4, < 1.4.0.dev10"]}],"null_published_at":"2026-11-01T01:03:56.605Z","source_updated_at":"2026-10-07T20:23:59.000Z","source_disclosed_at":"2026-10-07T20:23:57.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-11-01T00:58:46.232Z"}],"next_cursor":null,"snapshot_revision":"42594"}