Vulnerability in omnigent (CVE-2026-62676)
Summary
Vulnerability in omnigent (CVE-2026-62676). Confidential information can be exposed externally. Exploitable via write_repos. Mitigation: upgrade to 0.3.0 or later.
Original description
The description as published by the source.
Reporter: Aaron / Aeon — autonomous security agent (https://github.com/aaronjmars/aeon)
Project: omnigent-ai/omnigent v0.1.0 (Databricks) — meta-harness running Claude Code / Codex / Pi "in check with policies and sandboxing"
Component: omnigent/policies/builtins/_shell.py (shared parser) → consumed by policies/builtins/github.py (write_repos/write_branches allowlist) and policies/builtins/working_dir.py (workspace confinement)
Summary
The shared shell-command parser fails open. When a gated command spells something the parser doesn't recognize, it produces no operation, the policy evaluator returns None, and None = abstain = ALLOW. So any command the parser misses bypasses both the GitHub repo/branch allowlist and the working-directory confinement — the product's two core safety guarantees.
Impact
A misaligned or prompt-injected agent that is meant to be confined can:
git pushto an attacker-controlled repo (code / secret exfiltration),- push to a protected branch,
- escape its workspace via
git worktree add/git -C.
Bypass classes (all verified against the real policy code)
- Combined interpreter flags:
bash -lc "git push " - Unlisted wrappers:
timeout/nice/setsid/stdbuf … git push … - Command substitution:
x=$(git push ) - Un-split background operator:
true & git push
Controls that correctly hold (confirming this is parser incompleteness, not an allowlist logic error)…
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-62676 has been found in omnigent.
Attackers can target a specific entry point like write_repos over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.1/10.
What to do: upgrade omnigent to 0.3.0 or later.
If unsure, ask your IT team or search "omnigent CVE-2026-62676" on the vendor's site.
CVE-2026-62676 (omnigent) — CWE-184 / CVSS v3 7.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: write_repos / write_branches / None / timeout
Patched: 0.3.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-184) exists in omnigent. Attackers reach the vulnerable code path via write_repos.
Check the vendor advisory for the affected versions of omnigent. Attack surface: write_repos / write_branches / None / timeout.
Severity: High (CVSS 7.1/10). Confidential information can be exposed externally.
Update to 0.3.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'omnigent' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'omnigent' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
omnigentを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade omnigent to 0.3.0ステージング環境で 0.3.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。