hydra-optuna-sweeper is vulnerable to Unsafe Reflection
78
CVE Score
High
Unsafe Reflection
The Optuna sweeper's custom_search_space configuration option resolves a config-controlled dotted path with the lower-level hydra.utils.get_method() API and later invokes the returned callable. get_method() and its sibling object-lookup helpers intentionally trust their input and skip the execution policy used by instantiate(), so an Optuna multirun configuration or command-line override can select any importable callable in the application's environment for execution in the Hydra controller process. The selected code runs with the privileges of the application and requires only control over the sweep configuration plus an importable target. The fix resolves the configured callback through hydra.utils.instantiate() as a partial callable instead, so the active execution policy authorizes it before use.
Upgrade the hydra-optuna-sweeper library to the patch version.
You are affected if you are using a version that falls within the vulnerable range and you set the Optuna sweeper's custom_search_space option to a configuration-controlled or externally influenced dotted path.
1.2.0 - 1.2.0
Fixed in 1.3.0hydra-optuna-sweeper is vulnerable to Unsafe Reflection in versions 1.2.0 - 1.2.0.
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.