cve.bz

CVE-2026-106440 hydra-ecosystem hydra: Reflection Injection

7.8 highEPSS 0.3%Fix available

High (7.8) in hydra-ecosystem hydra. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in hydra-optuna-sweeper 1.3.0, 1.4.0.dev10.

On this page
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.

Severity

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 20th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-09. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-470 Use of Externally-Controlled Input to Select Classes or Code (Reflection Injection)
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • hydra-optuna-sweeper (PyPI): fixed in 1.3.0, 1.4.0.dev10

Ask an AI about this CVE

Show the promptExplain CVE-2026-106440 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-106440?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-106440?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-106440 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
hydra-ecosystem hydra>= 1.2.0, < 1.3.0
hydra-ecosystem hydra>= 1.4.0.dev4, < 1.4.0.dev10

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-5jjj-9xc3-rm56PyPIhydra-optuna-sweeper>=1.2.0 <1.3.01.3.0
GHSA-5jjj-9xc3-rm56PyPIhydra-optuna-sweeper>=1.4.0.dev4 <1.4.0.dev101.4.0.dev10
PYSEC-2026-4224PyPIhydra-optuna-sweeper>=1.2.0 <1.3.0
>=1.4.0.dev4 <1.4.0.dev10
1.3.0, 1.4.0.dev10

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as Important for Red Hat environments because successful exploitation can result in arbitrary code execution under the privileges of the running process. Exploitation requires user interaction to load untrusted sweep definitions or external parameter overrides. The affected component is not included in Red Hat Enterprise Linux, limiting exposure to environments that independently install and configure this framework.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-106440.

Attack patterns (CAPEC)

  • CAPEC-138 Reflection Injection Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON