CVE-2026-62675
Authenticated RCE in Omnigent via crafted agent bundles (fixed in v0.3.0).
Is CVE-2026-62675 being exploited?
Not confirmed. CVE-2026-62675 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.45% probability of exploitation in the next 30 days.
How severe is CVE-2026-62675?
CVE-2026-62675 is rated High with a CVSS score of 8.8. 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-62675?
Yes. A fix has been recorded for CVE-2026-62675. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-62675 affect?
CVE-2026-62675 affects Omnigent < 0.3.0, Omnigent server/runner, Deployments accepting multipart POST /v1/sessions bundles. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-62675?
Upgrade Omnigent to v0.3.0; block untrusted bundle uploads and harden runner permissions.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated remote code execution: attacker-supplied bundle can invoke subprocess.check_output to run OS commands, exfiltrate files, env vars, credentials, or disrupt runner.
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.