PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-62674 omnigent-ai CVE debrief

CVE-2026-62674 is a critical vulnerability in the Omnigent open-source AI agent framework. An authenticated user with edit access to a session can replace a shared agent bundle, leading to potential command execution with the Omnigent runner process permissions. This can result in exposure of files, credentials, workspace data, internal services, and runner availability. Omnigent users and administrators should assess their exposure and prioritize upgrading to version 0.3.0 or later. They should also verify session permissions and restrict access to LEVEL_EDIT.

Vendor
omnigent-ai
Product
omnigent
CVSS
CRITICAL 9
CISA KEV
Not listed in stored evidence
Original CVE published
2026-08-21
Original CVE updated
2026-09-18
Advisory published
2026-08-21
Advisory updated
2026-09-18

Who should care

Omnigent users and administrators should assess their exposure and prioritize upgrading to version 0.3.0 or later. They should also verify session permissions and restrict access to LEVEL_EDIT.

Why it matters

CVE-2026-62674 is a critical vulnerability in the Omnigent AI agent framework that allows an authenticated user to replace a shared agent bundle, leading to potential command execution. Omnigent users and administrators should assess their exposure and prioritize upgrading to version 0.3.0 or later.

  • Potential command execution with the Omnigent runner process permissions
  • Exposure of files, credentials, workspace data, internal services, and runner availability

Technical summary

The vulnerability is caused by the lack of proper validation of the agent.session_id in the PUT /sessions/{session_id}/agent endpoint. This allows an authenticated user with edit access to a session to replace a shared agent bundle with a malicious one, leading to potential command execution with the Omnigent runner process permissions. The command executes with the Omnigent runner process permissions and can expose files, credentials, workspace data, internal services, and runner availability. The issue is fixed in version 0.3.0.

Defensive priority

High priority for Omnigent users to upgrade to version 0.3.0 and verify session permissions.

Recommended defensive actions

  • Upgrade to Omnigent version 0.3.0 or later
  • Verify session permissions and restrict access to LEVEL_EDIT
  • Monitor for suspicious activity on the Omnigent runner process
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The vulnerability allows an authenticated user to replace a shared agent bundle through the PUT /sessions/{session_id}/agent endpoint, which checks LEVEL_EDIT permission but does not reject a bound shared or template agent with a null agent.session_id. This can lead to command execution with the Omnigent runner process permissions.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-62674 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-62674

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-62674 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-62674

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.