Hydra logging configuration permits unsafe callable resolution

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.8 · CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

EPSS

• CVE-2026-106441: 0.17% estimated exploitation activity in the next 30 days; percentile 5.82 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary 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. Fix Hydra now applies its target policy to callable resolution and invocation in Hydra-configured Python logging. It authorizes custom factories, handlers, formatters, filters, queues, listeners, aliases, discovery results, and callable results before they can be used. Hydra 1.3.6 uses the hardened blacklist. The Hydra 1.3 blacklist is a…

Published by the source

7 Oct 2026, 18:03 UTC

Last modified by the source

7 Oct 2026, 18:03 UTC

Source last checked

26 Oct 2026, 13:55 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-c3wx-c55w-pxjq

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-106441

Advisory: Hydra logging configuration permits unsafe callable resolution
IDs: CVE-2026-106441, GHSA-c3wx-c55w-pxjq
Record: https://patchnext.com/advisories/cve-2026-106441 (revision 1, source checked 26 Oct 2026, 13:55 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: hydra-core 1.4.0.dev9, 1.3.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI hydra-core: affected < 1.3.6; >= 1.4.0.dev0, < 1.4.0.dev9; fixed in 1.3.6, 1.4.0.dev9

## Suggested inspection (read-only)
- `python -m pip show hydra-core`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on hydra-core.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-c3wx-c55w-pxjq (GitHub-reviewed advisory GHSA-c3wx-c55w-pxjq lists affected ranges: PyPI hydra-core >=0 =1.4.0.dev0 <1.4.0.dev9)

Commands are suggestions: review each one before running it.