CVE-2026-62674: omnigent · Code Injection
Affects omnigentSource CVE Database V5
Not known to be exploited · CVSS 9.0 Critical : upgrade to 0.3.0 as a priority.
Data as of 20 Nov 2026, 17:35 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.3.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 21 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.
What to do
Upgrade omnigent and omnigent-ai/omnigent to 0.3.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| omnigent-aiomnigent | Affected
| Fixed in
|
GitHubomnigent-ai/omnigentpkg:github/omnigent-ai/omnigentOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade omnigent to version 0.3.0 or later, where this vulnerability is fixed. No other mitigations are specified. Since this is not a cloud service, remediation depends on applying the official fix.
Description
CVE-2026-62674 is a critical code injection vulnerability in the omnigent-ai omnigent framework prior to version 0.3.0. It allows an authenticated user with edit access to a session to replace a shared agent bundle lacking a session ID and inject attacker-controlled commands. These commands execute with the permissions of the Omnigent runner process, potentially exposing sensitive files, credentials, workspace data, internal services, and affecting runner availability. The issue is fixed in version 0.3.0.
References
- github.com/omnigent-ai/omnigent/security/advisories/GHSA-jrrm-9hc7-2v3h (opens in a new tab)
- github.com/omnigent-ai/omnigent/pull/1418 (opens in a new tab)
- github.com/omnigent-ai/omnigent/commit/25a22dc9e6da4648d23749f0a589e47e6aed991b (opens in a new tab)
- github.com/omnigent-ai/omnigent/releases/tag/v0.3.0 (opens in a new tab)