CVE-2026-106440highCWE-470

CVE-2026-106440: high-severity vulnerability in hydra-ecosystem hydra

Hydra: Optuna custom_search_space can resolve and execute untrusted callables via get_method

Published

21Vexday Risk Score

No sign of exploitation. No public exploitation artifact known so far.

ssvc Trackcvss 7.8epss 0.3%
exploitation probability
0.3%top 82% of all CVEs
observed exploitation
nono source reports it
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.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Affected products
hydra-ecosystem · hydra
Related CVEs — hydra-ecosystem hydra

In the same product, most dangerous first.

CVE-2026-106439HIGHHydra: Mutable instantiate policy sets allow target blocklist bypassEPSS 0.5%CVE-2026-106441HIGHHydra logging configuration permits unsafe callable resolutionEPSS 0.2%CVE-2026-106442HIGHHydra instantiate target blacklist bypasses permit code executionEPSS 0.2%
References
https://github.com/hydra-ecosystem/hydra/commit/0dd18084589a3d3e577d1f1a8a48fb485c94a5e6https://github.com/hydra-ecosystem/hydra/commit/4720dfca2bde27fa140ec287a05709668fbdf168https://github.com/hydra-ecosystem/hydra/releases/tag/v1.3.7https://github.com/hydra-ecosystem/hydra/security/advisories/GHSA-5jjj-9xc3-rm56