Is CVE-2026-106442 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-106442 being exploited in the wild.

How severe is CVE-2026-106442?

High severity, with a CVSS score of 7.8, published 6 October 2026.

Which products and versions are affected?

Facebook Hydra 1.3.4 to 1.3.6, 1.4.0.dev9; hydra-core (PyPI) ECOSYSTEM:introduced=1.3.4,fixed=1.3.6, ECOSYSTEM:introduced=1.3.4,fixed=1.3.6,introduced=1.4.0.dev0,fixed=1.4.0.dev9.

Is there a fix for CVE-2026-106442?

Yes. hydra-core (PyPI): upgrade to 1.3.6, 1.4.0.dev9 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-106442 attacked?

It is attacked with local access, in a software library.

Am I affected by CVE-2026-106442?

Check whether you run Facebook Hydra or hydra-core (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-106442: Facebook Hydra instantiate target bypass vulnerability

CVE-2026-106442 · Severity: high · CVSS 7.8 · Published 2026-10-06

Hydra is a Python framework used to configure complex applications. An incomplete authorization check in the instantiate() function allows attackers to execute arbitrary code by bypassing name-based blacklists through wrappers and aliases. If an application uses Hydra to load untrusted configuration files, an attacker could gain full control of the application.

Technologies: Facebook Hydra, hydra-core (PyPI). Vendors: Facebook, PyPI.

Quick answers

Is CVE-2026-106442 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-106442 being exploited in the wild.
How severe is CVE-2026-106442?: High severity, with a CVSS score of 7.8, published 6 October 2026.
Which products and versions are affected?: Facebook Hydra 1.3.4 to 1.3.6, 1.4.0.dev9; hydra-core (PyPI) ECOSYSTEM:introduced=1.3.4,fixed=1.3.6, ECOSYSTEM:introduced=1.3.4,fixed=1.3.6,introduced=1.4.0.dev0,fixed=1.4.0.dev9.
Is there a fix for CVE-2026-106442?: Yes. hydra-core (PyPI): upgrade to 1.3.6, 1.4.0.dev9 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-106442 attacked?: It is attacked with local access, in a software library.
Am I affected by CVE-2026-106442?: Check whether you run Facebook Hydra or hydra-core (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

hydra-core (PyPI): upgrade to 1.3.6, 1.4.0.dev9 or later
```
pip install "hydra-core>=1.4.0.dev9"
```

Technical details

The instantiate() target blacklist introduced in CVE-2026-68508 incompletely validates the effective callable, allowing bypass through execution wrappers (timeit.timeit), pickle deserialization, callable aliases, generic dispatch, and deferred calls. The vulnerability affects versions 1.3.4–1.3.6 and 1.4.0.dev9 and requires an attacker to influence configuration passed to instantiate(). The fix hardens authorization checks and enforces canonical resolved identities.

Affected products

Facebook Hydra 1.3.4 to 1.3.6, 1.4.0.dev9

Identifiers

CVE-2026-106442
GHSA-rqx7-p7vv-w7hr
PYSEC-2026-4223

Timeline

2026-10-06: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.