CVE-2026-62677
Path-traversal in Omnigent allows workspace escape, RCE and secret exposure.
Is CVE-2026-62677 being exploited?
Not confirmed. CVE-2026-62677 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-62677?
CVE-2026-62677 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-62677?
Yes. A fix has been recorded for CVE-2026-62677. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-62677 affect?
CVE-2026-62677 affects Omnigent < 0.3.0, Omnigent runner instances, Systems running Omnigent agent bundles. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-62677?
Upgrade Omnigent to >=0.3.0; restrict agent uploads and set OMNIGENT_RUNNER_WORKSPACE.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated agent upload can set cwd to escape runner workspace, enabling file read/write, shell execution, remote code execution and exfiltration of runner secrets.
Patch when possible
- 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.