CVE-2026-106441: Hydra logging configuration permits unsafe callable resolution
Hydra passed its Python logging configuration to logging.config.dictConfig(). Python’s logging configurator can resolve and invoke importable classes and factories named by configuration, including handler class values and formatter, filter, handler, queue, and listener () factories.
This logging path was not mediated by Hydra’s target policy. In versions that already protected instantiate(), logging resolution bypassed those controls because it did not use instantiate().
An attacker who can control a Hydra logging configuration can use a custom class or factory to execute code with the application’s privileges when Hydra configures logging.
References
- github.com/advisories/GHSA-c3wx-c55w-pxjq
- github.com/hydra-ecosystem/hydra/commit/76bfc30ce1f3105416941dd2e3a562568e369120
- github.com/hydra-ecosystem/hydra/commit/ff3e4dba890c29a21d8c2bb867ee87d37ccf21d0
- github.com/hydra-ecosystem/hydra/pull/3420
- github.com/hydra-ecosystem/hydra/releases/tag/v1.3.6
- github.com/hydra-ecosystem/hydra/security/advisories/GHSA-c3wx-c55w-pxjq
- nvd.nist.gov/vuln/detail/CVE-2026-106441
Code Behaviors & Features
Detect and mitigate CVE-2026-106441 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Dependency Scanning using SBOM also detects vulnerabilities from proprietary advisories that this site does not include. Learn more about Dependency Scanning using SBOM →