cve.bz

CVE-2026-106441 hydra-ecosystem hydra: Code Injection

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. Prior to 1.3.6 and 1.4.0.dev9, Hydra passes Python logging configuration to logging.config.dictConfig() without applying Hydra's target policy to handler class values or formatter, filter, handler, queue, and listener factories. An attacker who controls Hydra logging configuration can therefore select an importable class or factory and cause it to be invoked with the application's privileges, even in versions where instantiate() is protected because the logging path does not use instantiate(). 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; 6th 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-94 Improper Control of Generation of Code (Code Injection)
OWASP Top 10
A05:2025 Injection
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-106441 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-106441?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-106441?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-106441 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.6
hydra-ecosystem hydra>= 1.4.0.dev0, < 1.4.0.dev9

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-c3wx-c55w-pxjqPyPIhydra-core<1.3.61.3.6
GHSA-c3wx-c55w-pxjqPyPIhydra-core>=1.4.0.dev0 <1.4.0.dev91.4.0.dev9
PYSEC-2026-4221PyPIhydra-core<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 was found in the hydra-core Python framework, which Red Hat AI Inference Server and Red Hat Enterprise Linux AI (RHEL AI) ship as a dependency in their container images. Hydra passes Python logging configuration to logging.config.dictConfig() without applying its target policy to handler class values or to formatter, filter, handler, queue, and listener factories. As a result, an attacker who can supply or control a Hydra logging configuration can select an importable class or factory that is then invoked with the privileges of the running application, resulting in arbitrary code execution. Exploitation requires that a user or process run the application with an attacker-controlled configuration (CVSS 3.1 score 7.8, AV:L/AC:L/PR:N/UI:R), and the Red Hat severity of IMPORTANT matches the upstream rating. All affected Red Hat product streams are tracked as delegated affects, and a fix is being pursued by the responsible product 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. Upstream has fixed this issue in hydra-core 1.3.6 and 1.4.0.dev9; remediation for the affected Red Hat AI Inference Server and RHEL AI products will be delivered through their standard update channels once the fixed version is incorporated.

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-106441.

Attack patterns (CAPEC)

  • CAPEC-35 Leverage Executable Code in Non-Executable Files Likelihood: High · Severity: Very High
  • CAPEC-77 Manipulating User-Controlled Variables Likelihood: High · Severity: Very High
  • CAPEC-242 Code Injection Likelihood: High · Severity: High

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

References

Check your stackJSON