CVE-2026-106440

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (18th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
18th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

October 6, 2026

Last Modified

October 9, 2026

Advisory Details (4)

Auto-updated Oct 6, 2026
Patch available. Sources: github, github_commit, github_release.
github_release Patch Available

Hydra 1.3.7

Patch available: hydra-ecosystem/hydra v1.3.7

https://github.com/hydra-ecosystem/hydra/releases/tag/v1.3.7
github_commit Patch Available

commit 4720dfca2bde (hydra-ecosystem/hydra)

Patch available: hydra-ecosystem/hydra v1.3.7 (contains commit 4720dfca2bde)

https://github.com/hydra-ecosystem/hydra/commit/4720dfca2bde27fa140ec287a05709668fbdf168
github_commit

commit 0dd18084589a (hydra-ecosystem/hydra)

Fix landed in hydra-ecosystem/hydra commit 0dd18084589a — awaiting tagged release

https://github.com/hydra-ecosystem/hydra/commit/0dd18084589a3d3e577d1f1a8a48fb485c94a5e6
githubMentions a patch (unverified)

Optuna custom_search_space can resolve and execute untrusted callables via get_method · Advisory · hydra-ecosystem/hydra · GitHub

https://github.com/hydra-ecosystem/hydra/security/advisories/GHSA-5jjj-9xc3-rm56

Vendor Advisories for CVE-2026-106440(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
hydra-optuna-sweeper1.2.0, 1.3.0.dev0
  • 1.2.0 up to 1.3.0: fixed in 1.3.0
  • 1.4.0.dev4 up to 1.4.0.dev10: fixed in 1.4.0.dev10
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 10× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-09 20:06 UTCEPSS rescore
  2. 2026-10-09 02:18 UTCEG score recompute
  3. 2026-10-09 01:59 UTCEG score recompute
  4. 2026-10-08 20:25 UTCEG score recompute
  5. 2026-10-08 17:11 UTCEPSS rescore
  6. 2026-10-08 08:22 UTCEG score recompute
  7. 2026-10-07 23:47 UTCEPSS rescore
  8. 2026-10-06 19:33 UTCEG score recompute
  9. 2026-10-06 18:57 UTCEG score recompute
  10. 2026-10-06 18:57 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-106440?
CVE-2026-106440 is a high vulnerability published on October 6, 2026. 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.customsearchspace, resolves it with hydra.utils.getmethod(), and later invokes the returned…
When was CVE-2026-106440 disclosed?
CVE-2026-106440 was first published on October 6, 2026, with the most recent update on October 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-106440 actively exploited?
CVE-2026-106440 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (18th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-106440?
CVE-2026-106440 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-106440?
A fix for CVE-2026-106440 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-106440 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-106440

Explore →

Is Your Infrastructure Affected by CVE-2026-106440?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs