Categories
CVE-2026-106439

Vulnerability in hydra-core (CVE-2026-106439)

Summary

Vulnerability in hydra-core (CVE-2026-106439). Risk of unauthorized operations or information disclosure. Exploitable via _target_. Mitigation: upgrade to 1.4.0.dev10 or later.

Original description

The description as published by the source.

Summary

Hydra's legacy instantiate() target blocklists and related execution-policy
collections are stored in mutable module-level state. Because _locate() can
resolve attributes on imported objects, a configuration can resolve a mutation
method such as .discard(), modify the active policy, and then instantiate a
target that would otherwise be blocked.

Impact

A configuration controlling multiple sibling _target_ entries can first
remove an entry from a target blocklist and then invoke the removed target.
Sibling nodes are processed in insertion order and consult the same mutable
module-level policy.

This affects the legacy/default path without an execution whitelist. The 1.3
blocklist is a defense-in-depth measure rather than a complete security
boundary, and applications must not treat arbitrary untrusted configuration as
safe to instantiate or use for Python logging configuration.

Released hydra-core versions 1.3.4 through 1.3.6 and 1.4.0.dev4 through
1.4.0.dev9 are affected. Fixed releases are 1.3.7 and 1.4.0.dev10.
The reported direct mutation path does not bypass an execution whitelist
restricted to intended application targets and supplied by trusted Python
code. During remediation, Hydra additionally hardened generic discovery,
dispatch, introspection, alias, callable-result, and deferred-callable paths
that could otherwise undermine name-only authorization.

Technical details

In hydra-core 1.3.4 and 1.3.5, the mutable blocklist is reachable…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-106439 has been found in hydra-core.
Attackers can target a specific entry point like _target_ over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade hydra-core to 1.4.0.dev10 or later.
If unsure, ask your IT team or search "hydra-core CVE-2026-106439" on the vendor's site.

CVE-2026-106439 (hydra-core) — CWE-470
Attack surface: _target_ / hydra._internal.target_policy / set.discard / finally
Patched: 1.4.0.dev10 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-470) exists in hydra-core. Attackers reach the vulnerable code path via _target_.

📍 Affected scope

Check the vendor advisory for the affected versions of hydra-core. Attack surface: _target_ / hydra._internal.target_policy / set.discard / finally.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.4.0.dev10.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'hydra-core' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'hydra-core' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で hydra-core を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade hydra-core to 1.4.0.dev10

    ステージング環境で 1.4.0.dev10 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

pip hydra-core
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.4.0.dev10"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details