# Omnigent: Shared Agent Bundle Overwrite Leads to Authenticated Runner RCE

Advisory record · `GHSA-jrrm-9hc7-2v3h`

- **Identifiers:** `GHSA-jrrm-9hc7-2v3h` · `CVE-2026-62674` · `PYSEC-2026-3874`
- **State:** Confirmed
- **Severity:** CVSS 9.0 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-94](https://cwe.mitre.org/data/definitions/94.html)
- **Tags:** [Code injection](https://agentprime.io/advisories/tag/code-injection.md)
- **Published:** 2 Sept 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 2 Sept 2026, 21:55 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 9.0: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `omnigent` (PyPI): affected `<0.3.0`; fixed in `0.3.0`

## Machine-written summary

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

> Omnigent versions before 0.3.0 are affected. An authenticated user with edit access to their own session can upload a full agent bundle that overwrites a shared or template agent, adding a stdio MCP server whose command then runs as a subprocess of the runner in later sessions built from that agent. Upgrade to Omnigent 0.3.0 or later, which fixes the issue.

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

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

- **CISA KEV:** Not listed.
- **EPSS:** 0.0051, the 43rd percentile, on 12 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-jrrm-9hc7-2v3h)

## Sources

- [GitHub Advisory Database: GHSA-jrrm-9hc7-2v3h](https://github.com/advisories/GHSA-jrrm-9hc7-2v3h)
- [OSV: GHSA-jrrm-9hc7-2v3h](https://osv.dev/vulnerability/GHSA-jrrm-9hc7-2v3h)
- <https://github.com/omnigent-ai/omnigent/security/advisories/GHSA-jrrm-9hc7-2v3h>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-62674>
- <https://github.com/omnigent-ai/omnigent/pull/1418>
- <https://github.com/omnigent-ai/omnigent/commit/25a22dc9e6da4648d23749f0a589e47e6aed991b>
- <https://github.com/omnigent-ai/omnigent>
- <https://github.com/omnigent-ai/omnigent/releases/tag/v0.3.0>

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-jrrm-9hc7-2v3h>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-jrrm-9hc7-2v3h/>. Everything for agents: <https://agentprime.io/llms.txt>.