omnigent-ai Omnigent up to 0.2.x Agent sessions.py session_id permission

Summaryinfo

A vulnerability identified as critical has been detected in omnigent-ai Omnigent up to 0.2.x. This affects an unknown part of the file omnigent/server/routes/sessions.py of the component Agent. This manipulation of the argument session_id causes permission. This vulnerability is registered as CVE-2026-62674. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability classified as critical was found in omnigent-ai Omnigent up to 0.2.x. Affected by this vulnerability is some unknown functionality of the file omnigent/server/routes/sessions.py of the component Agent. The manipulation of the argument session_id with an unknown input leads to a permission vulnerability. The CWE definition for the vulnerability is CWE-275. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

Omnigent is an open-source AI agent framework and meta-harness for orchestrating coding agents. Prior to 0.3.0, PUT /sessions/{session_id}/agent checks LEVEL_EDIT permission for a session but does not reject a bound shared or template agent whose agent.session_id is None. An authenticated user with edit access to a session can replace that shared agent bundle through omnigent/server/routes/sessions.py, add a stdio MCP server, and cause later sessions that use the shared agent to launch an attacker-controlled command through omnigent/tools/mcp.py. The command executes with the Omnigent runner process permissions and can expose files, credentials, workspace data, internal services, and runner availability. This issue is fixed in version 0.3.0.

The advisory is shared at github.com. This vulnerability is known as CVE-2026-62674 since 07/14/2026. The exploitation appears to be easy. The attack can be launched remotely. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1222 for this issue.

Upgrading to version 0.3.0 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Artificial Intelligence Software

Vendor

• omnigent-ai

Name

• Omnigent

Version

• 0.1
• 0.2

Website

• Product: https://github.com/omnigent-ai/omnigent/

CPE 2.3info

• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion