Bug 2547635 (CVE-2026-106441) - CVE-2026-106441 hydra-core: hydra-core: Arbitrary code execution via unsafe logging configuration
Summary: CVE-2026-106441 hydra-core: hydra-core: Arbitrary code execution via unsafe l...
Keywords:
Status: NEW
Alias: CVE-2026-106441
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-10-07 19:01 UTC by OSIDB Bzimport
Modified: 2026-10-07 19:07 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-10-07 19:01:35 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.