CVE-2026-62677: Omnigent path traversal in agent bundle os_env.cwd

CVE-2026-62677 · Severity: high · CVSS 8.8 · Published 2026-08-21

Omnigent is an AI agent orchestration platform that allows users to upload custom agent bundles to be executed on runners. An authenticated user can craft a malicious agent bundle with an unrestricted working directory (cwd) to read, write, and modify files anywhere on the host system—and to exfiltrate runner environment secrets—if the runner is deployed without the OMNIGENT_RUNNER_WORKSPACE environment variable set. This bypasses intended filesystem isolation and gives attackers control equivalent to the runner process itself.

Technologies: omnigent (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2026-62677 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-62677 being exploited in the wild.
How severe is CVE-2026-62677?
High severity, with a CVSS score of 8.8, published 21 August 2026.
Which products and versions are affected?
omnigent (PyPI) < 0.3.0, ECOSYSTEM:introduced=0,fixed=0.3.0.
Is there a fix for CVE-2026-62677?
Yes. omnigent (PyPI): upgrade to 0.3.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-62677 attacked?
It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-62677?
Check whether you run omnigent (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • omnigent (PyPI): upgrade to 0.3.0 or later
    pip install "omnigent>=0.3.0"

Technical details

The vulnerability is a path traversal (CWE-22) in the agent bundle specification parser and validator. The os_env.cwd field in a bundle's config.yaml is parsed verbatim in omnigent/spec/parser.py:696 without validation, and the validator (_validate_os_env) never enforces boundaries on cwd. When a session-scoped uploaded bundle is realized on a runner that lacks the OMNIGENT_RUNNER_WORKSPACE guard, the attacker-controlled cwd is accepted as the root directory for all file and shell operations (os_env.py:890, resource_registry.py:648–654). An attacker sets cwd to "/" or "/home/victim" and sandbox.type to "none," then uses sys_os_read, sys_os_write, sys_os_edit, and sys_os_shell tools—bounded only by _assert_within_cwd—to traverse the entire host filesystem. This requires authentication and no admin privileges (only _require_user check). Patch 0.3.0 adds validation to reject absolute and traversal-prone cwd values; however, follow-up patches in 0.14.0 addressed additional upload paths for sub-agents and terminals that were not covered by the initial fix.

Affected products

  • Omnigent AI omnigent < 0.3.0 (root agent); additional paths in < 0.14.0 (sub-agents and terminals)

Identifiers

  • CVE-2026-62677
  • GHSA-p8rw-8qj3-hf33
  • PYSEC-2026-3875

Timeline

  • 2026-06-29: disclosed: Advisory GHSA-p8rw-8qj3-hf33 published by GitHub; initial reporter
  • 2026-06-26: patched: Root-agent fix merged in PR #1417; v0.3.0 released
  • 2026: patched: Follow-up patches in v0.14.0 for sub-agent and terminal paths (GHSA-p5x3-3gqh-x44g, GHSA-598r-29w2-g93q)
  • 2026-08-21: advisory: CVE-2026-62677 published by NVD
  • 2026-09-02: other: Advisory updated with follow-up fix information

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.