CVE-2026-106440: Hydra: Optuna custom_search_space can resolve and execute untrusted callables via get_method

Published Oct 6, 2026
·
Updated

Hydra is a framework for elegantly configuring complex applications. From 1.2.0 until 1.3.0 and 1.4.0.dev10, the hydra-optuna-sweeper package accepts a configuration-controlled dotted path in hydra.sweeper.customsearchspace, resolves it with hydra.utils.getmethod(), and later invokes the returned callable in the Hydra controller process. Because getmethod() is a trusted-input lookup helper and does not apply the execution policy used by instantiate(), an attacker who controls Optuna sweep configuration or command-line overrides can select importable Python code for execution with the application's privileges, including bypassing a trusted execution whitelist on affected Hydra 1.4 development releases. This issue is fixed in versions 1.3.0 and 1.4.0.dev10.

Affected Software

1 affected component
pypi/hydra-optuna-sweeper>=1.2.0<1.3.0, >=1.4.0.dev0<1.4.0.dev10

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade hydra-optuna-sweeper to a version that resolves this vulnerability.

    Fixed in 1.3.0
  2. Upgrade

    Upgrade hydra-optuna-sweeper to a version that resolves this vulnerability.

    Fixed in 1.4.0.dev10

Event History

Oct 6, 2026
CVE Published
via MITRE·06:51 PM
Data Sourced
via MITRE·06:51 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:18 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who is exposed to this issue?

Applications using the hydra-optuna-sweeper package are exposed if an attacker can control Optuna sweep configuration or supply command-line overrides that set hydra.sweeper.custom_search_space. The selected callable executes in the Hydra controller process with the application's privileges.

2

Are default deployments affected?

The issue requires attacker control of the relevant sweep configuration or command-line overrides. The provided information does not indicate that the default custom_search_space setting alone triggers exploitation.

3

What versions should be used to remediate the issue?

Upgrade to hydra-optuna-sweeper versions 1.3.0 or 1.4.0.dev10, which contain the fix. Affected versions are stated as 1.2.0 until those fixed releases.

4

What can be done if upgrading is not immediately possible?

Do not allow untrusted parties to modify Optuna sweep configuration or provide command-line overrides controlling hydra.sweeper.custom_search_space. Restrict this setting to trusted, reviewed callable paths.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203