CVE-2026-62674
Authenticated RCE via shared agent replacement in Omnigent <0.3.0
Is CVE-2026-62674 being exploited?
Not confirmed. CVE-2026-62674 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.34% probability of exploitation in the next 30 days.
How severe is CVE-2026-62674?
CVE-2026-62674 is rated Critical. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-62674?
Yes. A fix has been recorded for CVE-2026-62674. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-62674 affect?
CVE-2026-62674 affects Omnigent < 0.3.0, Omnigent server (sessions API), Shared/template agents, Omnigent runner process. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-62674?
Upgrade Omnigent to >=0.3.0; revoke/recreate shared agents; audit runner hosts and logs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated user with session edit can run arbitrary commands as the Omnigent runner, exfiltrate files/creds, and pivot to internal services.
Immediate action required
- affected< 0.3.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.