CVE-2026-62674

CRITICALPre-NVD 9.09.0—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 73% 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
9.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.0Exploit: 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, PUT /sessions/{session_id}/agent checks LEVEL_EDIT permission for a session but does not reject a bound shared or template agent whose agent.session_id is None. An authenticated user with edit access to a session can replace that shared agent bundle through omnigent/server/routes/sessions.py, add a stdio MCP server, and cause later sessions that use the shared agent to launch an attacker-controlled command through omnigent/tools/mcp.py. The command executes with the Omnigent runner process permissions and can expose files, credentials, workspace data, internal services, and runner availability. This issue is fixed in version 0.3.0.

CVSS v3
9.0
EG Score
9.0(medium)
EG Risk
41(Track)
EG Risk 41/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
Severity90% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
27%
KEV
Not listed

Published

August 21, 2026

Last Modified

August 25, 2026

Advisory Details (4)

Auto-updated Aug 21, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
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 25a22dc9e6da (omnigent-ai/omnigent)

Patch available: omnigent-ai/omnigent v0.3.0 (contains commit 25a22dc9e6da)

https://github.com/omnigent-ai/omnigent/commit/25a22dc9e6da4648d23749f0a589e47e6aed991b
github_pr Patch Available

fix(server): block shared-agent overwrite via bundle upload

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

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

Shared Agent Bundle Overwrite Leads to Authenticated Runner RCE · Advisory · omnigent-ai/omnigent · GitHub

https://github.com/omnigent-ai/omnigent/security/advisories/GHSA-jrrm-9hc7-2v3h

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 19× 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 05:08 UTCEG score recompute
  2. 2026-08-30 01:22 UTCEPSS rescore
  3. 2026-08-29 01:07 UTCEG score recompute
  4. 2026-08-28 21:42 UTCEPSS rescore
  5. 2026-08-27 18:18 UTCEG score recompute
  6. 2026-08-27 14:25 UTCEPSS rescore
  7. 2026-08-26 17:52 UTCEG score recompute
  8. 2026-08-26 14:46 UTCEPSS rescore
  9. 2026-08-25 18:28 UTCEG score recompute
  10. 2026-08-25 17:56 UTCEG score recompute
  11. 2026-08-25 14:10 UTCEG score recompute
  12. 2026-08-25 13:49 UTCEPSS rescore
  13. 2026-08-24 15:07 UTCEG score recompute
  14. 2026-08-24 11:18 UTCEG score recompute
  15. 2026-08-23 00:55 UTCEG score recompute
  16. 2026-08-23 00:19 UTCEPSS rescore
  17. 2026-08-21 18:18 UTCEG score recompute
  18. 2026-08-21 17:54 UTCEG score recompute
  19. 2026-08-21 17:54 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-62674?
CVE-2026-62674 is a critical 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, PUT /sessions/{sessionid}/agent checks LEVELEDIT permission for a session but does not reject a bound shared or template agent whose agent.session_id is None. An authenticated user with…
When was CVE-2026-62674 disclosed?
CVE-2026-62674 was first published in the National Vulnerability Database on August 21, 2026, with the most recent update on August 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-62674 actively exploited?
CVE-2026-62674 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 73.0% of all scored CVEs.
What is the CVSS score of CVE-2026-62674?
CVE-2026-62674 has a CVSS v3 base score of 9.0 (NVD).
How do I remediate CVE-2026-62674?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-62674, 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-62674

Explore →

Is Your Infrastructure Affected by CVE-2026-62674?

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

Start Free Scan →Browse All CVEs