Answer in brief
CVE-2026-106441 records a High severity (CVSS 7.8) vulnerability in Hydra logging configuration permits unsafe callable resolution. The current sources do not mark it as known exploited. The current feed maps hydra-ecosystem/hydra (generic), hydra-core (pip), hydra-core (pip). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps hydra-ecosystem/hydra (generic), hydra-core (pip), hydra-core (pip). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| hydra-ecosystem/hydrageneric | <1.3.6 || >=1.4.0.dev0 <1.4.0.dev9 | 1.3.6, 1.4.0.dev9 |
| hydra-corepip | <1.3.6 | 1.3.6 |
| hydra-corepip | >=1.4.0.dev0,<1.4.0.dev9 | 1.4.0.dev9 |
Published upstream
Oct 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 7, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 6, 2026
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.
Quoted source text, attributed separately from HOL analysis.