pypi package report

Is hydra-optuna-sweeper safe?

1 known vulnerability, worst severity HIGH.

// reach

2 direct dependencies

1 carry known advisories, worst HIGH

0 packages depend on it

an advisory here reaches each of them

    Create a free accountfor every dependency path, dependent and what to upgrade
    // ai model usage

    No published models are known to use this package.

    cvss
    0.0
    high

    severity out of 10

    epss
    not scored

    chance of exploitation in 30 days

    xyz score
    not scored

    CyberXYZ composite out of 10

    fig. 01 — GHSA-5jjj-9xc3-rm56, the advisory selected below

    // 1 advisories

    GHSA-5jjj-9xc3-rm56

    HIGHCVE-2026-106440
    // summary

    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 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 getobject(), getmethod(), getstaticmethod(), and getclass() 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.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 customsearchspace from externally controlled input or allow untrusted users to place modules on the application import path.

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

    // cvss v3.1 vector

    CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

    Attack vector
    Local
    Attack complexity
    Low
    Privileges required
    None
    User interaction
    Required
    Scope
    Unchanged
    Confidentiality
    High
    Integrity
    High
    Availability
    High

    Checked 2026-10-07 at 23:56 UTC. The most recent advisory here was published 2026-10-07. Updated continuously from NVD, GHSA, OSV and CNA feeds.

    Think a verdict here is wrong? Tell us — we respond within 2 business days.