Code Injection in omnigent (CVE-2026-62675)
Summary
Code injection in omnigent (CVE-2026-62675). Successful exploitation can lead to full system takeover. Exploitable via POST /v1/sessions. Mitigation: upgrade to 0.3.0 or later.
Original description
The description as published by the source.
Summary
An authenticated user can upload a crafted agent bundle that defines a server-side Python callable tool. The server validates the uploaded bundle, but it does not block dangerous callable: paths in untrusted user-provided agent configs.
When the tool is invoked, the runner imports and executes that Python callable. A crafted bundle can point the tool at subprocess.check_output, which lets the attacker run a local command on the runner machine.
This is serious because hosted Omnigent deployments can have multiple users and shared or managed runner hosts. A normal logged-in user should not be able to make the runner execute arbitrary local commands.
Details
The uploaded bundle path is reachable through session creation. Omnigent supports custom agent bundles through multipart POST /v1/sessions; the Web UI uses this same endpoint for custom agents:
Create custom agent builds and uploads a bundle
createBundledSession posts the bundle to /v1/sessions
A crafted bundle can also be submitted directly through the API/CLI when creating a session from agent YAML. The PoC below uses this direct bundle shape so the vulnerable trust boundary is easy to reproduce.
On the server, uploaded bund…
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-62675 has been found in omnigent.
Attackers can target a specific entry point like POST /v1/sessions over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: upgrade omnigent to 0.3.0 or later.
If unsure, ask your IT team or search "omnigent CVE-2026-62675" on the vendor's site.
CVE-2026-62675 (omnigent) — CWE-94 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /v1/sessions / subprocess.check_output / createBundledSession / validate_agent_bundle
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.
Arbitrary code execution (CWE-94) exists in omnigent. Attackers reach the vulnerable code path via POST /v1/sessions.
Check the vendor advisory for the affected versions of omnigent. Attack surface: POST /v1/sessions / subprocess.check_output / createBundledSession / validate_agent_bundle.
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.
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 POST /v1/sessions requests with malformed payloads or SQL meta-characters. 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 し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /v1/sessions' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /v1/sessionsへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade omnigent to 0.3.0ステージング環境で 0.3.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /v1/sessions on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。