Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%
Buy Us a Coffee

CVE-2026-106441— Hydra logging configuration permits unsafe callable resolution

Quick assessment

Affected
hydra-ecosystem hydra
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

Hydra 是一个用于优雅配置复杂应用程序的框架。在版本 1.3.6 及之前，以及 1.4.0.dev9 之前，Hydra 将 Python 的日志配置直接传递给 logging.config.dictConfig()，但未对处理器（handler）类值以及格式化器（formatter）、过滤器（filter）、处理器（handler）、队列（queue）和监听器（listener）工厂应用 Hydra 的实例化策略（target policy）。因此，如果攻击者能够控制 Hydra 的日志配置，便可以选择一个可导

CVSS 7.8 · High

Possible ATT&CK Techniques 1 AI

T1059 · Command and Scripting Interpreter

Affected Version Matrix 2

VendorProduct Version RangeStatus
hydra-ecosystem hydra < 1.3.6 affected
>= 1.4.0.dev0, < 1.4.0.dev9 affected
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-106441

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
Hydra logging configuration permits unsafe callable resolution
Source: CVE Program / CVE List V5
Vulnerability 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.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Source: CVE Program / CVE List V5
Vulnerability Type
对生成代码的控制不恰当(代码注入)
Source: CVE Program / CVE List V5

Affected Products

Vendor Product Affected Versions CPE Subscribe
hydra-ecosystem hydra < 1.3.6 -

II. Public POCs for CVE-2026-106441

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-106441

请登录查看更多情报信息。

Other References for CVE-2026-106441 (4)

Same Patch Batch · hydra-ecosystem · 2026-10-06 · 4 CVEs total

CVE-2026-106439 8.5 HIGH Hydra: Mutable instantiate policy sets allow target blocklist bypass
CVE-2026-106440 7.8 HIGH Hydra: Optuna custom_search_space can resolve and execute untrusted callables via get_meth
CVE-2026-106442 7.8 HIGH Hydra instantiate target blacklist bypasses permit code execution

IV. Related Vulnerabilities

Same product: hydra
Same vendor: hydra-ecosystem
Same weakness: CWE-94

V. Comments for CVE-2026-106441

No comments yet

Leave a comment