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

> Authenticated users can access arbitrary host files and secrets by uploading agent bundles with malicious working directory paths when runner workspace is unset.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Aug 2026
- **Updated:** 21 Aug 2026
- **Also known as:** GHSA-p8rw-8qj3-hf33, PYSEC-2026-3875

## What is CVE-2026-62677?

CVE-2026-62677 is a high-severity path traversal vulnerability in omnigent-ai omnigent, published on 21 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Omnigent is an open-source AI agent framework and meta-harness for orchestrating coding agents. Prior to 0.3.0, an authenticated user can upload a session-scoped agent bundle with an absolute or traversal-containing os_env.cwd value because omnigent/spec/parser.py stores the value verbatim and omnigent/spec/validator.py does not constrain it. On a runner where OMNIGENT_RUNNER_WORKSPACE is unset, omnigent/runner/resource_registry.py preserves the attacker-controlled path and omnigent/inner/os_env.py uses the resolved path as the environment root and copytree source. The _assert_within_cwd check then treats that attacker-selected root as trusted, allowing sys_os_read, write, edit, and shell tools to access runner files and environment secrets outside the intended workspace. This issue is fixed in version 0.3.0.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-62677?

3 open source packages ship an affected version, including omnigent.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `omnigent` | PyPI | All versions | 0.3.0 |
| `omnigent` | PyPI | All versions | 0.3.0 |
| `omnigent` | PyPI | All versions | 0.3.0 |

## How do I fix CVE-2026-62677?

Upgrade omnigent to 0.3.0 or later.

## Is CVE-2026-62677 being exploited?

There is no known exploitation of CVE-2026-62677 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-62677 and fix it if it is affected.

What it is: CVE-2026-62677 is a high-severity path traversal vulnerability in omnigent-ai omnigent, published on 21 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-62677 in the wild and no public exploit code.

Affected packages and fixed versions:
- omnigent (PyPI): affected all versions; fixed in 0.3.0
- omnigent (PyPI): affected all versions; fixed in 0.3.0
- omnigent (PyPI): affected all versions; fixed in 0.3.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-62677/ (Markdown: https://insights.sbomify.com/CVE-2026-62677/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-62677
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-62677
- OSV: https://osv.dev/vulnerability/CVE-2026-62677

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-62677/
Summaries are generated and may contain mistakes; the official description above is the record.