Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Tue, 06 Oct 2026 19:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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.custom_search_space, resolves it with hydra.utils.get_method(), and later invokes the returned callable in the Hydra controller process. Because get_method() 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. | |
| Title | Hydra: Optuna custom_search_space can resolve and execute untrusted callables via get_method | |
| Weaknesses | CWE-470 | |
| References |
|
|
| Metrics |
cvssV3_1
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-10-06T18:51:37.549Z
Reserved: 2026-10-06T16:49:40.590Z
Link: CVE-2026-106440
No data.
Status : Awaiting Analysis
Published: 2026-10-06T19:18:12.877
Modified: 2026-10-06T20:03:40.690
Link: CVE-2026-106440
No data.
OpenCVE Enrichment
No data.
-
CWE-470
Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection')