CVE-2026-62677

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 63% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Omnigent is an open-source AI agent framework and meta-harness for orchestrating coding agents. Prior to 0.3.0, an authenticated user can upload a session-scoped agent bundle with an absolute or traversal-containing os_env.cwd value because omnigent/spec/parser.py stores the value verbatim and omnigent/spec/validator.py does not constrain it. On a runner where OMNIGENT_RUNNER_WORKSPACE is unset, omnigent/runner/resource_registry.py preserves the attacker-controlled path and omnigent/inner/os_env.py uses the resolved path as the environment root and copytree source. The _assert_within_cwd check then treats that attacker-selected root as trusted, allowing sys_os_read, write, edit, and shell tools to access runner files and environment secrets outside the intended workspace. This issue is fixed in version 0.3.0.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
37%
KEV
Not listed

Published

August 21, 2026

Last Modified

August 21, 2026

Advisory Details (4)

Auto-updated Aug 21, 2026
Patch available. Sources: github_pr, github_commit, github_release, github.
github_release Patch Available

v0.3.0

Patch available: omnigent-ai/omnigent v0.3.0

https://github.com/omnigent-ai/omnigent/releases/tag/v0.3.0
github_commit Patch Available

commit 7ca0cca3c9a6 (omnigent-ai/omnigent)

Patch available: omnigent-ai/omnigent v0.3.0 (contains commit 7ca0cca3c9a6)

https://github.com/omnigent-ai/omnigent/commit/7ca0cca3c9a65c04c489edf68f0e080424a26868
github_pr Patch Available

fix(server): reject absolute/escaping os_env.cwd in uploaded agent bundles

Patch available: omnigent-ai/omnigent v0.3.0 (PR #1417 merged 2026-06-26)

https://github.com/omnigent-ai/omnigent/pull/1417
github Patch Available

Unvalidated os_env.cwd in agent bundle yields arbitrary host filesystem access on runners without OMNIGENT_RUNNER_WORKSPACE · Advisory · omnigent-ai/omnigent · GitHub

https://github.com/omnigent-ai/omnigent/security/advisories/GHSA-p8rw-8qj3-hf33

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 18× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-29 01:07 UTCEG score recompute
  3. 2026-08-28 21:42 UTCEPSS rescore
  4. 2026-08-27 20:34 UTCEG score recompute
  5. 2026-08-27 14:25 UTCEPSS rescore
  6. 2026-08-26 20:48 UTCEG score recompute
  7. 2026-08-26 14:46 UTCEPSS rescore
  8. 2026-08-25 21:09 UTCEG score recompute
  9. 2026-08-25 13:49 UTCEPSS rescore
  10. 2026-08-24 21:29 UTCEG score recompute
  11. 2026-08-24 09:36 UTCEG score recompute
  12. 2026-08-23 09:57 UTCEG score recompute
  13. 2026-08-23 00:19 UTCEPSS rescore
  14. 2026-08-21 22:25 UTCEG score recompute
  15. 2026-08-21 21:52 UTCEG score recompute
  16. 2026-08-21 18:18 UTCEG score recompute
  17. 2026-08-21 17:54 UTCEG score recompute
  18. 2026-08-21 17:54 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-62677?
CVE-2026-62677 is a high vulnerability published on August 21, 2026. Omnigent is an open-source AI agent framework and meta-harness for orchestrating coding agents. Prior to 0.3.0, an authenticated user can upload a session-scoped agent bundle with an absolute or traversal-containing osenv.cwd value because omnigent/spec/parser.py stores the value verbatim and…
When was CVE-2026-62677 disclosed?
CVE-2026-62677 was first published in the National Vulnerability Database on August 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-62677 actively exploited?
CVE-2026-62677 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 62.9% of all scored CVEs.
What is the CVSS score of CVE-2026-62677?
CVE-2026-62677 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-62677?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-62677, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-62677

Explore →

Is Your Infrastructure Affected by CVE-2026-62677?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs