CVSS 4.0
8.5 highCVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NHigh (8.5) in hydra-ecosystem hydra. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in hydra-core 1.3.7, 1.4.0.dev10.
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:Nhydra-core (PyPI): fixed in 1.3.7, 1.4.0.dev10Explain CVE-2026-106439 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-106439?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-106439?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-106439 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.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| hydra-ecosystem hydra | >= 1.3.4, < 1.3.7 |
| hydra-ecosystem hydra | >= 1.4.0.dev4, < 1.4.0.dev10 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-mwj6-rfh8-7qf4 | PyPI | hydra-core | >=1.3.4 <1.3.7 | 1.3.7 |
| GHSA-mwj6-rfh8-7qf4 | PyPI | hydra-core | >=1.4.0.dev4 <1.4.0.dev10 | 1.4.0.dev10 |
| PYSEC-2026-4222 | PyPI | hydra-core | >=1.3.4 <1.3.7 >=1.4.0.dev4 <1.4.0.dev10 | 1.3.7, 1.4.0.dev10 |
Red Hat rates this Important.
An Important severity flaw was found in hydra-core, which is bundled in Red Hat AI Inference Server 3.3 and 3.4 and Red Hat Enterprise Linux AI 3.4 container images. Hydra stores the target execution policies used during object instantiation in mutable module-level state. An attacker who can supply crafted configuration containing multiple sibling _target_ entries can resolve a mutation method on Hydra's internal target-policy collections (for example, the set.discard method of the uncontrolled-execution targets blocklist), remove a denied target from the policy, and then instantiate that otherwise-blocked target, because sibling nodes are processed in insertion order against the same process-global policy. Successful exploitation allows the attacker to execute arbitrary code with the permissions of the running application, and the policy mutation persists in process-global state for the lifetime of the Python process. Exploitation requires the application to instantiate attacker-influenced configuration on the legacy path without an execution whitelist; a narrow execution whitelist supplied by trusted Python code is not bypassed by the reported direct mutation path. A fix for the affected Red Hat products is being pursued. Red Hat rates this flaw as Important (CVSS 3.1 score 7.8); the upstream CVSS v4 score of 8.5 differs due to CVSS version and user-interaction metric differences rather than a different view of the vulnerability.
Avoid passing configuration from untrusted sources to Hydra's instantiate() or to Hydra-controlled Python logging configuration; restrict configuration input to trusted sources. On affected 1.4 development releases, applications can also supply a trusted, narrowly scoped execution whitelist from Python code, and the whitelist itself must not be derived from untrusted configuration. Restart any long-running process that may already have instantiated untrusted configuration, because a policy mutation persists in process-global state for the lifetime of the process. The upstream fix is available in hydra-core 1.3.7 on the stable line and 1.4.0.dev10 on the development line; for the affected Red Hat products, apply product updates containing the fixed version when they become available.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat AI Inference Server 3.5 | rhaii/vllm-cuda-rhel9:1791473631 | Fixed 2026-10-13 | RHSA-2026:82368 |
| Red Hat AI Inference Server 3.5 | rhaii/vllm-cpu-rhel9:1791473614 | Fixed 2026-10-13 | RHSA-2026:82415 |
| Red Hat Enterprise Linux AI 3.5 | rhelai3/disk-image-cuda-rhel9:1793206758 | Fixed 2026-10-29 | RHSA-2026:92449 |
| Red Hat Enterprise Linux AI 3.5 | rhelai3/bootc-aws-cuda-rhel9:1793194817 | Fixed 2026-10-29 | RHSA-2026:92452 |
| Red Hat Enterprise Linux AI 3.5 | rhelai3/bootc-azure-cuda-rhel9:1793194815 | Fixed 2026-10-29 | RHSA-2026:92452 |
| Red Hat Enterprise Linux AI 3.5 | rhelai3/bootc-cuda-rhel9:1793135861 | Fixed 2026-10-29 | RHSA-2026:92452 |
| Red Hat Enterprise Linux AI 3.5 | rhelai3/bootc-gcp-cuda-rhel9:1793194815 | Fixed 2026-10-29 | RHSA-2026:92452 |
| Red Hat AI Inference Server | rhaiis/vllm-cpu-rhel9 | Not affected | |
| Red Hat AI Inference Server | rhaiis/vllm-cuda-rhel9 | Not affected | |
| Red Hat AI Inference Server | rhaiis/vllm-rocm-rhel9 | Not affected | |
| Red Hat AI Inference Server | rhaiis/vllm-tpu-rhel9 | Not affected |
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-106439.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-693 (17).