cve.bz

CVE-2026-106442 hydra-ecosystem hydra: Incomplete List of Disallowed Inputs

7.8 highEPSS 0.2%Fix available

High (7.8) in hydra-ecosystem hydra. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in hydra-core 1.3.6, 1.4.0.dev9.

On this page
Hydra is a framework for elegantly configuring complex applications. From 1.3.4 until 1.3.6 and 1.4.0.dev9, the instantiate() target blacklist introduced for CVE-2026-68508 incompletely checks the effective callable selected by the target field. Execution wrappers such as timeit.timeit, executable deserialization through pickle.loads, aliases, callable-returning helpers, generic dispatch, and deferred calls can obscure or defer the effective target and bypass name-based authorization. An attacker who causes an application to instantiate untrusted Hydra configuration can use these gaps to execute code with the application's privileges. This issue is fixed in versions 1.3.6 and 1.4.0.dev9.

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.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 5th 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-07. 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-184 Incomplete List of Disallowed Inputs
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • hydra-core (PyPI): fixed in 1.3.6, 1.4.0.dev9

Ask an AI about this CVE

Show the promptExplain CVE-2026-106442 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-106442?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-106442?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-106442 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.3.4, < 1.3.6
hydra-ecosystem hydra>= 1.4.0.dev0, < 1.4.0.dev9

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-rqx7-p7vv-w7hrPyPIhydra-core>=1.3.4 <1.3.61.3.6
GHSA-rqx7-p7vv-w7hrPyPIhydra-core>=1.4.0.dev0 <1.4.0.dev91.4.0.dev9
PYSEC-2026-4223PyPIhydra-core>=1.3.4 <1.3.6
>=1.4.0.dev0 <1.4.0.dev9
1.3.6, 1.4.0.dev9

Red Hat

Red Hat rates this Important.

Red Hat's statement

A flaw of Important severity was found in the hydra-core Python configuration framework, which is bundled as a dependency in Red Hat AI Inference Server 3.3 and 3.4 and in Red Hat Enterprise Linux AI 3.4. Hydra's instantiate() mechanism does not properly validate the callable selected by the configuration target field against its blocklist: execution wrappers such as timeit.timeit, executable deserialization through pickle.loads, aliases, callable-returning helpers, generic dispatch, and deferred calls can obscure or defer the effective target and bypass the name-based authorization checks. An attacker who convinces an application or user to process an untrusted Hydra configuration file can use this flaw to execute arbitrary code with the privileges of the running application. Red Hat rates this flaw as Important (CVSS 3.1 score 7.8, AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), consistent with the upstream severity. The affected Red Hat products are tracked with a delegated resolution: the impact has been assessed and a fix is being pursued by the responsible engineering teams.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat AI Inference Server 3.5rhaii/vllm-cuda-rhel9:1791473631Fixed 2026-10-13RHSA-2026:82368
Red Hat AI Inference Server 3.5rhaii/vllm-cpu-rhel9:1791473614Fixed 2026-10-13RHSA-2026:82415
Red Hat Enterprise Linux AI 3.5rhelai3/disk-image-cuda-rhel9:1793206758Fixed 2026-10-29RHSA-2026:92449
Red Hat Enterprise Linux AI 3.5rhelai3/bootc-aws-cuda-rhel9:1793194817Fixed 2026-10-29RHSA-2026:92452
Red Hat Enterprise Linux AI 3.5rhelai3/bootc-azure-cuda-rhel9:1793194815Fixed 2026-10-29RHSA-2026:92452
Red Hat Enterprise Linux AI 3.5rhelai3/bootc-cuda-rhel9:1793135861Fixed 2026-10-29RHSA-2026:92452
Red Hat Enterprise Linux AI 3.5rhelai3/bootc-gcp-cuda-rhel9:1793194815Fixed 2026-10-29RHSA-2026:92452
Red Hat AI Inference Serverrhaiis/vllm-cpu-rhel9Not affected
Red Hat AI Inference Serverrhaiis/vllm-cuda-rhel9Not affected
Red Hat AI Inference Serverrhaiis/vllm-rocm-rhel9Not affected
Red Hat AI Inference Serverrhaiis/vllm-tpu-rhel9Not 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-106442.

Attack patterns (CAPEC)

  • CAPEC-3 Using Leading 'Ghost' Character Sequences to Bypass Input Filters Likelihood: Medium · Severity: Medium
  • CAPEC-6 Argument Injection Likelihood: High · Severity: High
  • CAPEC-15 Command Delimiters Likelihood: High · Severity: High
  • CAPEC-43 Exploiting Multiple Input Interpretation Layers Likelihood: Medium · Severity: High
  • CAPEC-71 Using Unicode Encoding to Bypass Validation Logic Likelihood: Medium · Severity: High
  • CAPEC-73 User-Controlled Filename Likelihood: High · Severity: High
  • CAPEC-85 AJAX Footprinting Likelihood: High · Severity: Low
  • CAPEC-120 Double Encoding Likelihood: Low · Severity: Medium
  • CAPEC-182 Flash Injection Likelihood: High · Severity: Medium

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

References

Check your stackJSON