CVE-2026-62676

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (32nd percentile of EPSS-scored CVEs). 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
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.1Exploit: 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, the shared shell-command parser in omnigent/policies/builtins/_shell.py fails to recognize combined interpreter flags, the timeout, nice, setsid, and stdbuf wrappers, command substitutions, and a single background control operator. A gated git push or gh write hidden with these forms produces no parsed operation, causing the github.py write_repos and write_branches allowlist and the working_dir.py workspace confinement policies to abstain and allow the command. An authenticated or prompt-injected agent can therefore push to an unauthorized repository or branch or escape the intended workspace. This issue is fixed in version 0.3.0.

CVSS v3
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
32
EG Risk 32/100CISA SSVC

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
Severity71% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
32nd
KEV
Not listed

CISA SSVCTrack at every mission impact level.

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

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 1a05b7b139ef (omnigent-ai/omnigent)

Patch available: omnigent-ai/omnigent v0.3.0 (contains commit 1a05b7b139ef)

https://github.com/omnigent-ai/omnigent/commit/1a05b7b139ef504bf2be89bf37918abe104fb95c
github_pr Patch Available

fix(policies): broaden shell-command parser to close gate-bypass disguises (GHSA-7mqg)

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

https://github.com/omnigent-ai/omnigent/pull/389
githubMentions a patch (unverified)

Guardrail policy bypass: shell-command parser fails open (CWE-184) in policies/builtins/_shell.py · Advisory · omnigent-ai/omnigent · GitHub

https://github.com/omnigent-ai/omnigent/security/advisories/GHSA-7mqg-cx4g-x2rf

Vendor Advisories for CVE-2026-62676(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 12× in last 7d / 47× 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-10-10 20:00 UTCEPSS rescore
  2. 2026-10-09 20:07 UTCEPSS rescore
  3. 2026-10-09 05:51 UTCEG score recompute
  4. 2026-10-08 17:13 UTCEPSS rescore
  5. 2026-10-08 04:55 UTCEG score recompute
  6. 2026-10-07 23:48 UTCEPSS rescore
  7. 2026-10-06 19:46 UTCEG score recompute
  8. 2026-10-06 15:18 UTCEPSS rescore
  9. 2026-10-06 07:49 UTCEG score recompute
  10. 2026-10-05 17:43 UTCEPSS rescore
  11. 2026-10-05 04:54 UTCEG score recompute
  12. 2026-10-04 23:22 UTCEPSS rescore
  13. 2026-10-03 16:42 UTCEG score recompute
  14. 2026-10-03 14:26 UTCEPSS rescore
  15. 2026-10-02 20:59 UTCEG score recompute
  16. 2026-10-02 17:56 UTCEPSS rescore
  17. 2026-10-01 21:25 UTCEG score recompute
  18. 2026-10-01 19:50 UTCEPSS rescore
  19. 2026-09-30 20:28 UTCEG score recompute
  20. 2026-09-30 15:03 UTCEPSS rescore
  21. 2026-09-29 16:11 UTCEG score recompute
  22. 2026-09-29 01:53 UTCEG score recompute
  23. 2026-09-27 14:40 UTCEG score recompute
  24. 2026-09-27 02:28 UTCEG score recompute
  25. 2026-09-26 15:59 UTCEPSS rescore
Show 59 more
  1. 2026-09-24 19:31 UTCEG score recompute
  2. 2026-09-23 20:02 UTCEG score recompute
  3. 2026-09-23 17:54 UTCEPSS rescore
  4. 2026-09-22 20:09 UTCEG score recompute
  5. 2026-09-22 08:25 UTCEG score recompute
  6. 2026-09-20 20:40 UTCEG score recompute
  7. 2026-09-20 20:16 UTCEPSS rescore
  8. 2026-09-19 19:45 UTCEG score recompute
  9. 2026-09-18 20:17 UTCEG score recompute
  10. 2026-09-18 19:28 UTCEPSS rescore
  11. 2026-09-18 00:06 UTCEG score recompute
  12. 2026-09-16 23:24 UTCEG score recompute
  13. 2026-09-16 14:08 UTCEPSS rescore
  14. 2026-09-16 11:39 UTCEG score recompute
  15. 2026-09-16 05:15 UTCEPSS rescore
  16. 2026-09-15 11:34 UTCEG score recompute
  17. 2026-09-13 23:54 UTCEG score recompute
  18. 2026-09-13 00:26 UTCEG score recompute
  19. 2026-09-12 00:57 UTCEG score recompute
  20. 2026-09-11 14:53 UTCEPSS rescore
  21. 2026-09-11 13:13 UTCEG score recompute
  22. 2026-09-11 09:37 UTCEPSS rescore
  23. 2026-09-10 13:45 UTCEG score recompute
  24. 2026-09-09 01:46 UTCEG score recompute
  25. 2026-09-08 22:01 UTCEPSS rescore
  26. 2026-09-08 03:20 UTCEG score recompute
  27. 2026-09-07 16:01 UTCEPSS rescore
  28. 2026-09-06 15:48 UTCEG score recompute
  29. 2026-09-06 13:47 UTCEPSS rescore
  30. 2026-09-05 16:19 UTCEG score recompute
  31. 2026-09-05 15:31 UTCEPSS rescore
  32. 2026-09-04 16:51 UTCEG score recompute
  33. 2026-09-04 05:07 UTCEPSS rescore
  34. 2026-09-02 17:11 UTCEG score recompute
  35. 2026-09-02 14:12 UTCEPSS rescore
  36. 2026-09-01 17:42 UTCEG score recompute
  37. 2026-09-01 13:54 UTCEPSS rescore
  38. 2026-09-01 05:57 UTCEG score recompute
  39. 2026-09-01 04:40 UTCEPSS rescore
  40. 2026-08-31 04:51 UTCEG score recompute
  41. 2026-08-30 19:17 UTCEPSS rescore
  42. 2026-08-30 05:23 UTCEG score recompute
  43. 2026-08-30 01:22 UTCEPSS rescore
  44. 2026-08-29 05:49 UTCEG score recompute
  45. 2026-08-28 21:42 UTCEPSS rescore
  46. 2026-08-27 18:33 UTCEG score recompute
  47. 2026-08-27 14:25 UTCEPSS rescore
  48. 2026-08-26 18:24 UTCEG score recompute
  49. 2026-08-26 18:07 UTCEG score recompute
  50. 2026-08-26 16:14 UTCEG score recompute
  51. 2026-08-26 14:46 UTCEPSS rescore
  52. 2026-08-25 16:28 UTCEG score recompute
  53. 2026-08-25 13:49 UTCEPSS rescore
  54. 2026-08-24 16:56 UTCEG score recompute
  55. 2026-08-23 05:29 UTCEG score recompute
  56. 2026-08-23 00:19 UTCEPSS rescore
  57. 2026-08-21 18:18 UTCEG score recompute
  58. 2026-08-21 17:54 UTCEG score recompute
  59. 2026-08-21 17:54 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-62676?
CVE-2026-62676 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, the shared shell-command parser in omnigent/policies/builtins/shell.py fails to recognize combined interpreter flags, the timeout, nice, setsid, and stdbuf wrappers, command…
When was CVE-2026-62676 disclosed?
CVE-2026-62676 was first published on August 21, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-62676 actively exploited?
CVE-2026-62676 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (32nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-62676?
CVE-2026-62676 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-62676?
A fix for CVE-2026-62676 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-62676 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-62676

Explore →

Is Your Infrastructure Affected by CVE-2026-62676?

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

Book a Demo →Browse All CVEs