Skip to main content
VulnerabilityPublished

CVE-2026-106439: hydra · Unsafe Reflection

Affects hydraSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.5 High : upgrade to 1.4.0.dev10 or 1.3.7 soon.

Data as of 20 Nov 2026, 17:34 UTC

CVSS 4.0 base score
8.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.4.0.dev10, 1.3.7
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

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.dev10 or 1.3.7.

Affected software

ProductAffectedFixed in
hydra-ecosystemhydraAffected
  • >=1.4.0.dev4 <1.4.0.dev10
Fixed in
  • 1.4.0.dev10
hydra-ecosystemhydraAffected
  • >=1.3.4 <1.3.7
Fixed in
  • 1.3.7
PyPIhydra-ecosystem/hydrapkg:pypi/hydra-ecosystem/hydraOther threatsAffected
  • >=1.3.4 <1.3.7
  • >=1.4.0.dev4 <1.4.0.dev10
Fixed in
  • 1.3.7
  • 1.4.0.dev10

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

AI-suggested

A fix is available in hydra-core versions 1.3.7 and 1.4.0.dev10 that makes policy state immutable and enforces stricter authorization checks. Users should upgrade to these versions. Until upgraded, users must ensure that only trusted configuration is passed to instantiate() and Hydra-controlled Python logging configuration, as the 1.3 release line lacks an execution whitelist. On affected 1.4 development releases, applications can supply a trusted execution whitelist from Python code. Additionally, restart any long-running processes that may have instantiated untrusted configuration to clear mutated policy state.

Description

CVE-2026-106439 is a high-severity vulnerability in hydra-ecosystem's hydra affecting versions 1.3.4 through 1.3.6 and 1.4.0.dev4 through 1.4.0.dev9. It involves unsafe reflection where mutable module-level state used for target blocklists can be manipulated via configuration to remove blocked targets and instantiate them, bypassing intended execution restrictions. The vulnerability affects the legacy/default path without an execution whitelist and allows a configuration controlling multiple sibling _target_ entries to mutate the blocklist and invoke otherwise blocked targets. The issue is fixed in hydra-core 1.3.7 and 1.4.0.dev10. Users are advised to upgrade and avoid passing untrusted configuration to instantiate().

References

Community reviews

Loading reviews…