Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
HIGH severity

CVE-2026-106440 — hydra-optuna-sweeper

HIGHFix: hydra-ecosystem/hydra@0dd1808

CVE-2026-106440 is a high-severity (CVSS 7.8) CWE-470 vulnerability in hydra-optuna-sweeper. A fix is available for hydra-optuna-sweeper — see the affected versions and patch details below.

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

Also known asGHSA-5jjj-9xc3-rm56PYSEC-2026-4224
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Oct 23, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • A successful exploit gives an attacker total control of the affected component, not partial access.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-106440.

EPSS Exploitation Probability

via FIRST.org ↗
0.3%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs19th percentile — riskier than 19% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2026-106440 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 394,803 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

2 pkgs affected
🐍hydra-optuna-sweeper🐍hydra-optuna-sweeper

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

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 configuration and directs config-driven construction to instantiate().

Affected versions

  • Package: hydra-optuna-sweeper
  • Stable affected range: >= 1.2.0, < 1.3.0
  • Stable fixed version: 1.3.0
  • Development affected range: >= 1.4.0.dev4, < 1.4.0.dev10
  • Development fixed version: 1.4.0.dev10

The feature was introduced in 1.2.0 and is absent from the 1.1 release line. The 1.4 development line was affected from 1.4.0.dev4 through 1.4.0.dev9.

Workaround

Treat Optuna sweep configuration and command-line overrides as trusted. Do not set custom_search_space from externally controlled input or allow untrusted users to place modules on the application import path.

Reported by zx (GitHub: @manus-pi).

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIhydra-optuna-sweeper≥ 1.2.0&&< 1.3.01.3.0pip install --upgrade 'hydra-optuna-sweeper==1.3.0'
🐍PyPIhydra-optuna-sweeper≥ 1.4.0.dev4&&< 1.4.0.dev101.4.0.dev10pip install --upgrade 'hydra-optuna-sweeper==1.4.0.dev10'

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for hydra-optuna-sweeper, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update hydra-optuna-sweeper to 1.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-106440 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

## 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 configura
O3 Security · Impact-Aware SCA

Is CVE-2026-106440 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works