CVE-2026-62677

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6% (47th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.8HIGHmedium confidence
EG Risk
40
EG Risk 40/100

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 (value × EchelonGraph’s weight)
Severity88% × 45%
The EG Score, 8.8 of 10.
Exploitation0.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.6%
EPSS %ILE
47th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 21, 2026

Last Modified

September 18, 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 pull request 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 advisoryMentions a patch (unverified)

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

Vendor Advisories for CVE-2026-62677(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
omnigent0.0.1rc1 ... 0.3.0rc1 (12 versions)
  • every version up to 0.3.0: fixed in 0.3.0
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 51× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  2. 2026-10-13 12:16 UTCEG score recompute
  3. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  4. 2026-10-12 15:49 UTCEG score recompute
  5. 2026-10-11 19:33 UTCEG score recompute
  6. 2026-10-11 16:49 UTCEG score recompute
  7. 2026-10-11 14:10 UTCEG score recompute
  8. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  10. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  11. 2026-10-09 05:51 UTCEG score recompute
  12. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  13. 2026-10-08 04:55 UTCEG score recompute
  14. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  15. 2026-10-06 21:18 UTCEG score recompute
  16. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  17. 2026-10-05 20:34 UTCEG score recompute
  18. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  19. 2026-10-05 08:44 UTCEG score recompute
  20. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  21. 2026-10-03 16:42 UTCEG score recompute
  22. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  23. 2026-10-02 21:35 UTCEG score recompute
  24. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  25. 2026-10-01 21:25 UTCEG score recompute
Show 71 more
  1. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  2. 2026-09-30 20:28 UTCEG score recompute
  3. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  4. 2026-09-29 16:11 UTCEG score recompute
  5. 2026-09-29 02:27 UTCEG score recompute
  6. 2026-09-28 14:37 UTCEG score recompute
  7. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  8. 2026-09-27 14:40 UTCEG score recompute
  9. 2026-09-27 02:28 UTCEG score recompute
  10. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  11. 2026-09-24 19:46 UTCEG score recompute
  12. 2026-09-23 20:05 UTCEG score recompute
  13. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  14. 2026-09-22 20:26 UTCEG score recompute
  15. 2026-09-22 08:36 UTCEG score recompute
  16. 2026-09-20 20:45 UTCEG score recompute
  17. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  18. 2026-09-19 19:56 UTCEG score recompute
  19. 2026-09-18 20:17 UTCEG score recompute
  20. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  21. 2026-09-18 00:06 UTCEG score recompute
  22. 2026-09-16 23:55 UTCEG score recompute
  23. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  24. 2026-09-16 12:05 UTCEG score recompute
  25. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  26. 2026-09-15 12:25 UTCEG score recompute
  27. 2026-09-14 00:45 UTCEG score recompute
  28. 2026-09-13 01:05 UTCEG score recompute
  29. 2026-09-12 01:26 UTCEG score recompute
  30. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  31. 2026-09-11 13:36 UTCEG score recompute
  32. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  33. 2026-09-10 13:56 UTCEG score recompute
  34. 2026-09-09 01:46 UTCEG score recompute
  35. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  36. 2026-09-07 22:53 UTCEG score recompute
  37. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  38. 2026-09-06 23:09 UTCEG score recompute
  39. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  40. 2026-09-05 23:30 UTCEG score recompute
  41. 2026-09-05 15:31 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  42. 2026-09-04 23:48 UTCEG score recompute
  43. 2026-09-04 11:53 UTCEG score recompute
  44. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  45. 2026-09-02 23:51 UTCEG score recompute
  46. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  47. 2026-09-02 00:05 UTCEG score recompute
  48. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  49. 2026-09-01 12:14 UTCEG score recompute
  50. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  51. 2026-08-31 00:34 UTCEG score recompute
  52. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  53. 2026-08-30 12:44 UTCEG score recompute
  54. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  55. 2026-08-29 01:07 UTCEG score recompute
  56. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  57. 2026-08-27 20:34 UTCEG score recompute
  58. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  59. 2026-08-26 20:48 UTCEG score recompute
  60. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  61. 2026-08-25 21:09 UTCEG score recompute
  62. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  63. 2026-08-24 21:29 UTCEG score recompute
  64. 2026-08-24 09:36 UTCEG score recompute
  65. 2026-08-23 09:57 UTCEG score recompute
  66. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  67. 2026-08-21 22:25 UTCEG score recompute
  68. 2026-08-21 21:52 UTCEG score recompute
  69. 2026-08-21 18:18 UTCEG score recompute
  70. 2026-08-21 17:54 UTCEG score recomputeFirst assessed: 8.8 HIGH
  71. 2026-08-21 17:54 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-62677?
CVE-2026-62677 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-62677 published?
The CVE record for CVE-2026-62677 was published on August 21, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 18, 2026; the record at its source may have been updated since.
Is CVE-2026-62677 actively exploited?
CVE-2026-62677 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (47th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-62677?
CVE-2026-62677 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-62677?
A fix for CVE-2026-62677 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-62677 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by 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.

Book a Demo →Browse All CVEs