hydra-core is vulnerable to Unsafe Reflection
85
CVE Score
High
Unsafe Reflection
Hydra's _locate() dotted-path resolver performs a plain getattr attribute walk that can reach mutation methods such as .discard() on the module level policy sets (DEFAULT_BLOCKLISTED_MODULES, UNCONTROLLED_EXECUTION_TARGETS) backing the default instantiate() execution blocklist. A configuration with multiple sibling _target_ entries, processed in insertion order, can first resolve and call a removal method on the shared policy set and then instantiate the now unblocked target, bypassing the legacy blocklist path used when an application has not supplied its own execution whitelist. The fix moves target resolution off the raw mutable sets and hardens the discovery, dispatch, introspection, alias, callable-result, and deferred-callable paths so name only authorization can no longer be undermined this way.
Upgrade the hydra-core library to the patch version.
You are affected if you are using a version that falls within the vulnerable range and you rely on Hydra's default instantiate() blocklist without supplying your own execution whitelist to authorize targets.
1.3.4 - 1.3.6
Fixed in 1.3.7hydra-core is vulnerable to Unsafe Reflection in versions 1.3.4 - 1.3.6.
Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.
No credit card required | Scan results in 32 seconds.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.