Skip to content

← Public intelligence

PyPI package

hydra-optuna-sweeper

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 7.8PyPIPublished

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

    CVE-2026-106440 · GHSA-5jjj-9xc3-rm56

    Affected
    • PyPI hydra-optuna-sweeper >= 1.2.0, < 1.3.0; >= 1.4.0.dev4, < 1.4.0.dev10
    Fixed in
    1.3.01.4.0.dev10· Vendor fix available
    Issue
    hydra-optuna-sweeper accepted a configuration-controlled dotted path in hydra.sweeper.customsearchspace, resolved it with the lower-level hydra.utils.getmethod() 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…

    Recommended action: Upgrade to 1.4.0.dev10 (pre-release) or 1.3.0 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →