# Hydra: Mutable instantiate policy sets allow target blocklist bypass Advisory record · `GHSA-mwj6-rfh8-7qf4` - **Identifiers:** `GHSA-mwj6-rfh8-7qf4` · `CVE-2026-106439` · `PYSEC-2026-4222` - **State:** Confirmed - **Severity:** CVSS 8.5 High - **Critical:** No - **Weakness (CWE):** [CWE-470](https://cwe.mitre.org/data/definitions/470.html) · [CWE-693](https://cwe.mitre.org/data/definitions/693.html) - **Tags:** [Code injection](https://agentprime.io/advisories/tag/code-injection.md) · [CWE-693](https://agentprime.io/advisories/tag/cwe-693.md) - **Published:** 7 Oct 2026 - **Updated:** 15 Oct 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 7 Oct 2026, 20:23 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `hydra-core` (PyPI): affected `>=1.3.4, <1.3.7 || >=1.4.0.dev4, <1.4.0.dev10`; fixed in `1.3.7`, `1.4.0.dev10` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > Hydra (hydra-core) versions 1.3.4 to before 1.3.7 and 1.4.0.dev4 to before 1.4.0.dev10 store their instantiate target blocklists in mutable module-level state, so a configuration that can resolve and call a set-mutation method can remove a blocked target and then instantiate it. An attacker who can supply untrusted configuration can thereby run targets that would otherwise be blocked. Upgrade to hydra-core 1.3.7 or 1.4.0.dev10, and do not pass untrusted configuration to instantiate(); the advisory describes no separate fix for the 1.3 line. Written 1 Nov 2026. ## Not analysed yet We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check. ## Severity and exploitation - 8.5 High, CVSS 4.0: `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`, from CNA (GitHub_M) - **CISA KEV:** Not listed. - **EPSS:** 0.0046, the 39th percentile, on 7 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 14:08 UTC: First seen by agentprime - 31 Oct 2026, 14:08 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-mwj6-rfh8-7qf4) ## Sources - [GitHub Advisory Database: GHSA-mwj6-rfh8-7qf4](https://github.com/advisories/GHSA-mwj6-rfh8-7qf4) - [OSV: GHSA-mwj6-rfh8-7qf4](https://osv.dev/vulnerability/GHSA-mwj6-rfh8-7qf4) - - - - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .