Omnigent
Omnigent: Unvalidated os_env.cwd in agent bundle yields arbitrary host filesystem access on runners without OMNIGENT_RUNNER_WORKSPACE
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 0.3.0
Fixed in 0.3.0
Mitigation
Upgrade omnigent to 0.3.0 or later.
References
- Vendor advisory github.com/omnigent-ai/omnigent/security/advis…
- Patch github.com/omnigent-ai/omnigent/pull/1417
- Patch github.com/omnigent-ai/omnigent/commit/7ca0cca…
1 more
- Release notes github.com/omnigent-ai/omnigent/releases/tag/v…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.