# Hydra: hydra.utils.instantiate with untrusted config can lead to code execution

Advisory record · `GHSA-2cp2-2r3c-7p7r`

- **Identifiers:** `GHSA-2cp2-2r3c-7p7r` · `CVE-2026-68508` · `PYSEC-2026-3850`
- **State:** Confirmed
- **Severity:** CVSS 7.8 High
- **Critical:** No
- **Weakness (CWE):** [CWE-94](https://cwe.mitre.org/data/definitions/94.html) · [CWE-470](https://cwe.mitre.org/data/definitions/470.html)
- **Tags:** [Code injection](https://agentprime.io/advisories/tag/code-injection.md)
- **Published:** 21 Aug 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 21 Aug 2026, 20:57 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`; fixed in `1.3.4`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Hydra (hydra-core) versions before 1.3.4 are vulnerable when hydra.utils.instantiate() is given untrusted config, because an attacker who controls the \_target\_ value and its arguments can run arbitrary code in the calling process. Exploitation requires an application to load attacker-controlled config, overrides, or metadata and pass it to instantiate(). Upgrade to hydra-core 1.3.4 or later. Until then, validate \_target\_ values against a trusted allowlist before instantiation.

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

- 7.8 High, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0046, the 40th percentile, on 13 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:10 UTC: First seen by agentprime
- 31 Oct 2026, 14:10 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-2cp2-2r3c-7p7r)

## Sources

- [GitHub Advisory Database: GHSA-2cp2-2r3c-7p7r](https://github.com/advisories/GHSA-2cp2-2r3c-7p7r)
- [OSV: GHSA-2cp2-2r3c-7p7r](https://osv.dev/vulnerability/GHSA-2cp2-2r3c-7p7r)
- <https://github.com/hydra-ecosystem/hydra/security/advisories/GHSA-2cp2-2r3c-7p7r>
- <https://github.com/hydra-ecosystem/hydra/issues/3259>
- <https://github.com/hydra-ecosystem/hydra/pull/3261>
- <https://github.com/hydra-ecosystem/hydra/commit/7faad0dcedfb4c0a364aa1067c0080fd6fdf8dca>
- <https://github.com/hydra-ecosystem/hydra>
- <https://github.com/hydra-ecosystem/hydra/releases/tag/v1.3.4>

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 (<https://api.agentprime.io/mcp>), 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: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-2cp2-2r3c-7p7r>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-2cp2-2r3c-7p7r/>. Everything for agents: <https://agentprime.io/llms.txt>.