Vulnerability in hydra-optuna-sweeper (CVE-2026-106440)
Summary
Vulnerability in hydra-optuna-sweeper (CVE-2026-106440). Successful exploitation can lead to full system takeover. Exploitable via hydra.sweeper.custom_search_space. Mitigation: upgrade to 1.4.0.dev10 or later.
Original description
The description as published by the source.
Summary
hydra-optuna-sweeper accepted a configuration-controlled dotted path in
hydra.sweeper.custom_search_space, resolved it with the lower-level
hydra.utils.get_method() API, and later invoked the returned callable.
Hydra's object-lookup helpers intentionally trust their input and do not apply
the execution policy used by instantiate() and logging configuration. As a
result, untrusted Optuna multirun configuration could select installed Python
code for execution in the Hydra controller process.
Impact
Exploitation requires control of an application's Optuna sweep configuration
or command-line overrides and an importable callable in the application's
environment. Selected code runs with the privileges of the application.
On affected Hydra 1.4 development releases, this path bypasses an execution
whitelist provided by trusted application code. Hydra 1.3 has no execution-whitelist
security boundary; there, the same change restores the legacy blocklist as
defense in depth.
Fix
The Optuna sweeper now resolves the configured callback through
hydra.utils.instantiate() as a partial callable. On Hydra 1.4, the active
execution whitelist therefore authorizes the callback before use. On Hydra
1.3, the legacy blocklist is applied as defense in depth.
The public get_object(), get_method(), get_static_method(), and
get_class() helpers remain lower-level trusted-input APIs. Their documentation
now warns against passing values derived from untrusted conf…
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-106440 has been found in hydra-optuna-sweeper.
Attackers can target a specific entry point like hydra.sweeper.custom_search_space over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 7.8/10.
What to do: upgrade hydra-optuna-sweeper to 1.4.0.dev10 or later.
If unsure, ask your IT team or search "hydra-optuna-sweeper CVE-2026-106440" on the vendor's site.
CVE-2026-106440 (hydra-optuna-sweeper) — CWE-470 / CVSS v3 7.8
Attack vector: local / unauthenticated
Attack surface: hydra.sweeper.custom_search_space / custom_search_space
Patched: 1.4.0.dev10 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-470) exists in hydra-optuna-sweeper. Attackers reach the vulnerable code path via hydra.sweeper.custom_search_space without authentication.
Check the vendor advisory for the affected versions of hydra-optuna-sweeper. Attack surface: hydra.sweeper.custom_search_space / custom_search_space.
Severity: High (CVSS 7.8/10). Successful exploitation can lead to full system takeover.
Update to 1.4.0.dev10.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'hydra-optuna-sweeper' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'hydra-optuna-sweeper' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
hydra-optuna-sweeperを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade hydra-optuna-sweeper to 1.4.0.dev10ステージング環境で 1.4.0.dev10 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- package pypi.org
- web github.com
- web github.com
- web github.com
- web github.com