CVE-2026-106439

HIGHPre-NVD 8.58.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 8.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (39th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 4 sources updated this weekElevated

Also known asEUVD-2026-93658 (ENISA EUVD) · GHSA-mwj6-rfh8-7qf4 (GitHub Security Advisories)Source: ENISA EUVD

8.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Hydra is a framework for elegantly configuring complex applications. From 1.3.4 until 1.3.7 and 1.4.0.dev10, Hydra stores legacy instantiate target blocklists and related execution-policy collections in mutable module-level state. An attacker who controls multiple sibling target entries can resolve hydra._internal.target_policy.UNCONTROLLED_EXECUTION_TARGETS.discard through instantiate(), remove a denied target, and then invoke that target because sibling nodes are processed in insertion order against the same modified policy. The mutation persists in process-global state and can enable code execution with the application's privileges, while a narrow execution whitelist supplied by trusted Python code is not bypassed by the reported direct mutation path. This issue is fixed in versions 1.3.7 and 1.4.0.dev10.

CVSS v3
8.5
EG Score
8.5HIGHmedium confidence
EG Risk
54
EG Risk 54/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity85% × 45%
Impact severity (EG Severity): CVSS 8.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
39th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.5): severity, escalated by confirmed exploitation. This CVE's 8.5 is its impact severity (EG Severity), not escalated.

EG Severity
8.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 6, 2026

Last Modified

October 6, 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
GitHub advisoryMentions a patch (unverified)

Mutable instantiate policy sets allow target blocklist bypass · Advisory · hydra-ecosystem/hydra · GitHub

https://github.com/hydra-ecosystem/hydra/security/advisories/GHSA-mwj6-rfh8-7qf4

Vendor Advisories for CVE-2026-106439(5)

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

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhaii/vllm-cpu-rhel9:17914736142026-10-13redhat
redhatrhaii/vllm-cuda-rhel9:17914736312026-10-13redhat
piphydra-core @ 1.3.7 (fixes >= 1.3.4, < 1.3.7)—ghsa
piphydra-core @ 1.4.0.dev10 (fixes >= 1.4.0.dev4, < 1.4.0.dev10)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
hydra-core1.4.0.dev4, 1.4.0.dev5, 1.4.0.dev6, 1.4.0.dev8, 1.4.0.dev9
  • 1.3.4 up to 1.3.7: fixed in 1.3.7
  • 1.4.0.dev4 up to 1.4.0.dev10: fixed in 1.4.0.dev10
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 51× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-02 16:43 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  2. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  3. 2026-11-01 08:00 UTCGHSA enrichmentGHSA-mwj6-rfh8-7qf4 · GitHub severity HIGH
  4. 2026-11-01 08:00 UTCEG score recompute
  5. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  6. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  7. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  8. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  9. 2026-10-27 20:38 UTCEG score recompute
  10. 2026-10-27 20:38 UTCVendor advisory
  11. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  12. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  13. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  14. 2026-10-25 14:54 UTCEG score recompute
  15. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  16. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  17. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  18. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  19. 2026-10-20 19:12 UTCEG score recompute
  20. 2026-10-20 19:12 UTCVendor advisory
  21. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  22. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  23. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  24. 2026-10-18 05:08 UTCEG score recompute
  25. 2026-10-17 19:24 UTCEG score recompute
Show 26 more
  1. 2026-10-17 19:24 UTCVendor advisory
  2. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  3. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  4. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  5. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  6. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  7. 2026-10-12 16:39 UTCEG score recompute
  8. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  9. 2026-10-11 20:14 UTCEG score recompute
  10. 2026-10-11 18:27 UTCEG score recompute
  11. 2026-10-11 15:00 UTCEG score recompute
  12. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  13. 2026-10-10 20:42 UTCEG score recompute
  14. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  15. 2026-10-09 20:43 UTCEG score recompute
  16. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  17. 2026-10-08 20:43 UTCEG score recompute
  18. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  19. 2026-10-08 08:45 UTCEG score recompute
  20. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  21. 2026-10-06 20:34 UTCEG score recompute
  22. 2026-10-06 20:11 UTCEG score recompute
  23. 2026-10-06 20:00 UTCEG score recompute
  24. 2026-10-06 19:33 UTCEG score recompute
  25. 2026-10-06 18:57 UTCEG score recomputeFirst assessed: 8.5 HIGH
  26. 2026-10-06 18:57 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-106439?
CVE-2026-106439 is a high-severity vulnerability; its CVE record was published on October 6, 2026. Hydra is a framework for elegantly configuring complex applications. From 1.3.4 until 1.3.7 and 1.4.0.dev10, Hydra stores legacy instantiate target blocklists and related execution-policy collections in mutable module-level state. An attacker who controls multiple sibling target entries can resolve…
When was the CVE record for CVE-2026-106439 published?
The CVE record for CVE-2026-106439 was published on October 6, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 6, 2026; the record at its source may have been updated since.
Is CVE-2026-106439 actively exploited?
CVE-2026-106439 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (39th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-106439?
CVE-2026-106439 has a CVSS base score of 8.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-106439?
A fix for CVE-2026-106439 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-106439 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-106439

Explore →

Is Your Infrastructure Affected by CVE-2026-106439?

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

Book a Demo →Browse All CVEs