CVE-2026-106439 hydra-ecosystem CVE debrief

Who should care

Defenders managing Hydra configurations, especially those using the legacy/default path without an execution whitelist, should assess exposure and apply patches to affected versions.

Why it matters

The vulnerability in Hydra's legacy `instantiate()` target blocklists allows for target blocklist bypass due to mutable module-level state, affecting `hydra-core` versions 1.3.4 through 1.3.6 and 1.4.0.dev4 through 1.4.0.dev9. Defenders should prioritize verifying exposure and applying patches.

• Verify and prioritize patching of affected `hydra-core` versions to prevent potential target blocklist bypass
• Review and update Hydra configurations to ensure they are not using the vulnerable legacy/default path without an execution whitelist
• Assess the security posture of systems using Hydra for Python logging configuration to prevent potential exploitation

Technical summary

The vulnerability arises from Hydra's legacy `instantiate()` target blocklists and related execution-policy collections being stored in mutable module-level state. A configuration can resolve a mutation method, modify the active policy, and then instantiate a target that would otherwise be blocked. This affects `hydra-core` versions 1.3.4 through 1.3.6 and 1.4.0.dev4 through 1.4.0.dev9. Fixed releases are 1.3.7 and 1.4.0.dev10. Defenders should prioritize verifying exposure and applying patches, especially for configurations using the legacy/default path without an execution whitelist.

Defensive priority

Defenders should prioritize verifying exposure in their Hydra configurations, especially those using the legacy/default path without an execution whitelist, and apply patches to affected versions.

Recommended defensive actions

• Verify and apply patches to affected `hydra-core` versions
• Review Hydra configurations for legacy/default path usage without an execution whitelist
• Update to fixed versions 1.3.7 or 1.4.0.dev10
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The vulnerability is confirmed in `hydra-core` versions 1.3.4 through 1.3.6 and 1.4.0.dev4 through 1.4.0.dev9 with explicit evidence from source references. Patches are available in versions 1.3.7 and 1.4.0.dev10. Defenders should verify exposure and apply patches, especially for configurations using the legacy/default path without an execution whitelist.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.