Executive brief
Omnigent is an open-source AI agent framework that manages sessions and agent bundles. An authenticated user can exploit a missing authorization check to overwrite shared/template agents that are intentionally marked as non-editable. By injecting malicious code into the agent bundle, the attacker can execute arbitrary commands on the runner host with the permissions of the Omnigent process, affecting all future sessions that use the poisoned shared agent. In shared or company deployments, this enables attackers to steal credentials, modify data, disrupt availability, or establish persistent shell access.
Technical details
The vulnerability is a missing authorization guard in the full agent bundle upload endpoint (PUT /sessions/{session_id}/agent). The endpoint checks session edit permissions but fails to verify whether the target agent is a shared/template agent (identified by agent.session_id is None). Other parts of the API correctly block such modifications for shared agents, but the full bundle upload endpoint bypasses this check. An authenticated attacker can upload a crafted agent bundle containing a stdio MCP server that executes an arbitrary command. Since stdio MCP servers launch their configured command as local subprocesses running with the runner process's privileges, the injected command executes with full runner permissions. The fix (applied in version 0.3.0) adds the missing guard to prevent modifications to shared/template agents. The vulnerability requires authentication and user interaction but has broad impact: scope change (C:H, I:H, A:H) with network attack vector.
Affected products
- omnigent-ai omnigent < 0.3.0
Timeline
- 2026-09-02: disclosed: Published on GitHub Advisory Database
- 2026-06-29: patched: Fix available in version 0.3.0
- 2026-08-21: advisory: Published to NVD