Skip to main content
VulnerabilityPublished

CVE-2026-106441: hydra · Code Injection

Affects hydraSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.8 High : upgrade to 1.4.0.dev9 or 1.3.6 soon.

Data as of 20 Nov 2026, 17:34 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.4.0.dev9, 1.3.6
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

Upgrade hydra and hydra-ecosystem/hydra to 1.4.0.dev9 or 1.3.6.

Affected software

ProductAffectedFixed in
hydra-ecosystemhydraAffected
  • >=1.4.0.dev0 <1.4.0.dev9
Fixed in
  • 1.4.0.dev9
hydra-ecosystemhydraAffected
  • <1.3.6
Fixed in
  • 1.3.6
PyPIhydra-ecosystem/hydrapkg:pypi/hydra-ecosystem/hydraOther threatsAffected
  • <1.3.6
  • >=1.4.0.dev0 <1.4.0.dev9
Fixed in
  • 1.3.6
  • 1.4.0.dev9

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade to Hydra version 1.3.6 or later, or to 1.4.0.dev9 or later for the 1.4 prerelease line, where the vulnerability is addressed by applying target policies to logging callable resolution. On Hydra 1.3, avoid composing logging configurations from untrusted sources. On Hydra 1.4 and later, use a narrow execution whitelist supplied by trusted Python code to constrain custom logging targets. Refer to https://hydra.cc/docs/advanced/execution_whitelist/ for guidance on configuring the execution whitelist. These measures ensure that only authorized callables are invoked during logging configuration.

Description

CVE-2026-106441 is a high-severity code injection vulnerability in the hydra-ecosystem hydra project. The issue arises because Hydra passed its Python logging configuration directly to logging.config.dictConfig() without applying its target policy, allowing resolution and invocation of arbitrary importable classes and factories. This flaw enables an attacker who can control the logging configuration to execute arbitrary code with the application's privileges during logging setup. The vulnerability affects Hydra versions before 1.3.6 and prerelease versions from 1.4.0.dev0 up to but not including 1.4.0.dev9. Hydra 1.3.6 and later apply a hardened blacklist, and 1.4.0.dev9 and later introduce an execution whitelist to control callable invocation securely. Users are advised to upgrade to 1.3.6 or 1.4.0.dev9 or later and avoid composing logging configurations from untrusted sources.

References

Community reviews

Loading reviews…