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.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
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
Which versions are affected by CVE-2026-62677?
3 open source packages ship an affected version, including omnigent.
| Package | 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.
Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.
Is CVE-2026-62677 being exploited?
There is no known exploitation of CVE-2026-62677 in the wild and no public exploit code.
Sources
Also known as GHSA-p8rw-8qj3-hf33, PYSEC-2026-3875.