CVE-2026-106441

Hydra logging configuration permits unsafe callable resolution

Published Oct 6, 2026 CVSS 3.1 · 7.8 High EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

Hydra is a framework for configuring complex applications. Prior to 1.3.6 and 1.4.0.dev9, it passes Python logging configuration to logging.config.dictConfig() without applying Hydra's target policy to handler class values, 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 unsafe callable resolution is a classic code‑injection flaw that can lead to arbitrary code execution and full compromise of the application.

Affected Systems

Hydra releases that precede version 1.3.6 and the 1.4.0.dev9 development release carry the bug because the framework passes unfiltered logging configuration to dictConfig() without applying Hydra’s target policy. Any deployment that uses those older versions and accepts user‑supplied logging configuration is vulnerable. The issue is resolved in 1.3.6 and later, as well as in 1.4.0.dev9 and newer releases.

Risk and Exploitability

The CVSS base score of 7.8 indicates a high importance of this weakness. EPSS score of <1% shows a very low current exploitation probability. The vulnerability is not listed in the CISA KEV catalog. The likely attack vector is any path by which an attacker can influence Hydra’s logging configuration—such as a misconfigured web interface, API, or configuration repository. If the underlying process runs with elevated privileges, execution of the injected callable elevates the attacker to the same level, constituting a severe breach of confidentiality, integrity, and availability.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Hydra to version 1.3.6 or later (including 1.4.0.dev9 and newer releases). This update removes the unsafe callable resolution that is the root cause of CWE-94 and mitigates the older code injection risks described in CWE-470.
  • Restrict write access to logging configuration files or inputs to trusted administrators or processes only to prevent Unauthorized injection of malicious classes; this controls the attack surface for CWE-94 and CWE-470.
  • If an immediate upgrade is not possible, enforce a target policy on all logging configuration values or replace the unsafe dictConfig call with a strictly validated configuration routine to block arbitrary callable resolution, thereby addressing the code injection weaknesses highlighted by CWE-94 and ensuring safe handler instantiation per CWE-470.

Generated by OpenCVE AI on October 8, 2026 at 14:46 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-c3wx-c55w-pxjq Hydra logging configuration permits unsafe callable resolution
History
Type Values Removed Values Added
First Time appeared Hydra-ecosystem
Hydra-ecosystem hydra
Vendors & Products Hydra-ecosystem
Hydra-ecosystem hydra
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description 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.
Title Hydra logging configuration permits unsafe callable resolution
Weaknesses CWE-94
References
Metrics cvssV3_1

{'score': 7.8, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H'}

Weaknesses
  • CWE-470

    Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection')

  • CWE-94

    Improper Control of Generation of Code ('Code Injection')

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Oct 7, 2026, 6:49 PM
Reserved
Oct 6, 2026, 4:49 PM
Status
Awaiting Analysis
Published
Oct 6, 2026, 7:18 PM
Modified
Oct 7, 2026, 7:17 PM
Severity
Important
Public date
Oct 6, 2026, 6:53 PM