# Omnigent: Unvalidated os_env.cwd in agent bundle yields arbitrary host filesystem access on runners without OMNIGENT_RUNNER_WORKSPACE

Advisory record · `GHSA-p8rw-8qj3-hf33`

- **Identifiers:** `GHSA-p8rw-8qj3-hf33` · `CVE-2026-62677` · `PYSEC-2026-3875`
- **State:** Confirmed
- **Severity:** CVSS 8.8 High
- **Critical:** No
- **Weakness (CWE):** [CWE-22](https://cwe.mitre.org/data/definitions/22.html)
- **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md)
- **Published:** 2 Sept 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

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

## 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 let an authenticated user gain arbitrary read and write access to the host filesystem on a runner, and read the runner's environment secrets, by uploading an agent bundle whose os_env cwd points outside the intended workspace. This applies only to runners where OMNIGENT_RUNNER_WORKSPACE is not set. Upgrade to Omnigent 0.3.0 or later. Setting OMNIGENT_RUNNER_WORKSPACE on runners is a deployment-level mitigation, though the source notes it is not a complete defense.

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.8 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0061, the 49th 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-p8rw-8qj3-hf33)

## Sources

- [GitHub Advisory Database: GHSA-p8rw-8qj3-hf33](https://github.com/advisories/GHSA-p8rw-8qj3-hf33)
- [OSV: GHSA-p8rw-8qj3-hf33](https://osv.dev/vulnerability/GHSA-p8rw-8qj3-hf33)
- <https://github.com/omnigent-ai/omnigent/security/advisories/GHSA-p8rw-8qj3-hf33>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-62677>
- <https://github.com/omnigent-ai/omnigent/pull/1417>
- <https://github.com/omnigent-ai/omnigent/commit/7ca0cca3c9a65c04c489edf68f0e080424a26868>
- <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-p8rw-8qj3-hf33>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-p8rw-8qj3-hf33/>. Everything for agents: <https://agentprime.io/llms.txt>.