CVE-2026-88062

CRITICALPre-NVD 9.59.5
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 1.4% (72nd 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
Trending — 3 sources updated this week

Also known asEUVD-2026-75705 (ENISA EUVD) · GHSA-hf57-cqmx-p4gr (GitHub Security Advisories)Source: ENISA EUVD

9.5EG
EchelonGraph verdictPlan mitigationNo fix is confirmed yet: check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.4%CVSS: 9.5Exploit: None knownExposed services: Not assessed

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

OmniRoute is an open-source AI gateway providing a single endpoint for multiple model providers. In 3.8.49 and earlier, the OmniRoute POST /api/acp/agents custom ACP agent endpoint accepted attacker-controlled binary and versionCommand values and used only a self-consistency check before execFileSync executed the selected interpreter and arguments. The same request called refreshAgentCache, and resolveVersionProbe accepted the matched command before the execFileSync sink ran it. The tokenizeVersionCommand function and DISALLOWED_VERSION_COMMAND_CHARS filter rejected a limited set of shell metacharacters but still allowed interpreter evaluation arguments. The isAuthenticated function relied on isAuthRequired, which accepted anonymous requests when requireLogin was false, while api/acp/ was absent from LOCAL_ONLY_API_PREFIXES and SPAWN_CAPABLE_PREFIXES. With requireLogin=false or during a fresh-instance bootstrap window, a remote anonymous request could supply an interpreter evaluation argument and execute arbitrary code in the server container. With requireLogin=true and a configured management password, exploitation instead required a management session or management-scoped API key. No fixed version is available as of this review.

CVSS v3
9.5
EG Score
9.5CRITICALmedium confidence
EG Risk
43
EG Risk 43/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity95% × 45%
Impact severity (EG Severity): CVSS 9.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation1.4% × 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: No fix is confirmed yet. Check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule.
EPSS PROB
1.4%
EPSS %ILE
72nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.5): severity, escalated by confirmed exploitation. This CVE's 9.5 is its impact severity (EG Severity), not escalated.

EG Severity
9.5 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
1.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

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

No fix is confirmed yet. Check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule.

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.

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.

The score's inputs: 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

September 10, 2026

Last Modified

September 30, 2026

Advisory Details (3)

Auto-updated Oct 2, 2026
No fix on record yet. Sources: github_commit, github_pr, github.
GitHub advisoryMentions a patch (unverified)

OmniRoute ACP Custom-Agent Remote Code Execution (RCE) · Advisory · diegosouzapw/OmniRoute · GitHub

https://github.com/diegosouzapw/OmniRoute/security/advisories/GHSA-hf57-cqmx-p4gr
GitHub pull request

fix(security): close the open security advisories for v3.8.50

Fix merged in diegosouzapw/OmniRoute PR #11028 on 2026-08-21 — awaiting tagged release

https://github.com/diegosouzapw/OmniRoute/pull/11028
GitHub commit

commit 60829241fd64 (diegosouzapw/OmniRoute)

Fix landed in diegosouzapw/OmniRoute commit 60829241fd64 — awaiting tagged release

https://github.com/diegosouzapw/OmniRoute/commit/60829241fd64d0317aa6a0dd8cd7a445a5287fed

Vendor Advisories for CVE-2026-88062(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmomniroute—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
omniroute—
  • every version through 3.8.50: no fix on record
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 18× in last 7d / 117× 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.

Showing the most recent 100 of 294 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 194 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 16:46 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  2. 2026-11-02 10:23 UTCEG score recompute
  3. 2026-11-02 10:23 UTCGHSA enrichmentGHSA-hf57-cqmx-p4gr · GitHub severity CRITICAL
  4. 2026-11-01 08:58 UTCEG score recompute
  5. 2026-11-01 08:58 UTCGHSA enrichmentGHSA-hf57-cqmx-p4gr · GitHub severity CRITICAL
  6. 2026-10-31 16:33 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  7. 2026-10-31 07:34 UTCEG score recompute
  8. 2026-10-31 07:34 UTCGHSA enrichmentGHSA-hf57-cqmx-p4gr · GitHub severity CRITICAL
  9. 2026-10-30 16:35 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  10. 2026-10-30 06:12 UTCEG score recompute
  11. 2026-10-30 06:12 UTCGHSA enrichmentGHSA-hf57-cqmx-p4gr · GitHub severity CRITICAL
  12. 2026-10-29 16:34 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  13. 2026-10-29 04:50 UTCEG score recompute
  14. 2026-10-29 04:50 UTCGHSA enrichmentGHSA-hf57-cqmx-p4gr · GitHub severity CRITICAL
  15. 2026-10-28 16:33 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  16. 2026-10-28 03:24 UTCEG score recompute
  17. 2026-10-28 03:24 UTCGHSA enrichmentGHSA-hf57-cqmx-p4gr · GitHub severity CRITICAL
  18. 2026-10-27 16:32 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  19. 2026-10-27 01:53 UTCEG score recompute
  20. 2026-10-27 01:53 UTCGHSA enrichmentGHSA-hf57-cqmx-p4gr · GitHub severity CRITICAL
  21. 2026-10-26 16:32 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  22. 2026-10-25 20:31 UTCEG score recompute
  23. 2026-10-25 20:31 UTCGHSA enrichmentGHSA-hf57-cqmx-p4gr · GitHub severity CRITICAL
  24. 2026-10-25 16:34 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  25. 2026-10-25 13:53 UTCEG score recompute
Show 75 more
  1. 2026-10-24 19:09 UTCEG score recompute
  2. 2026-10-24 19:08 UTCGHSA enrichmentGHSA-hf57-cqmx-p4gr · GitHub severity CRITICAL
  3. 2026-10-24 16:34 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  4. 2026-10-23 17:44 UTCEG score recompute
  5. 2026-10-23 17:44 UTCGHSA enrichmentGHSA-hf57-cqmx-p4gr · GitHub severity CRITICAL
  6. 2026-10-23 16:32 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  7. 2026-10-22 16:35 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  8. 2026-10-22 16:20 UTCEG score recompute
  9. 2026-10-22 16:20 UTCGHSA enrichmentGHSA-hf57-cqmx-p4gr · GitHub severity CRITICAL
  10. 2026-10-21 16:34 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  11. 2026-10-21 14:43 UTCEG score recompute
  12. 2026-10-21 14:43 UTCGHSA enrichmentGHSA-hf57-cqmx-p4gr · GitHub severity CRITICAL
  13. 2026-10-20 16:33 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  14. 2026-10-20 13:19 UTCEG score recompute
  15. 2026-10-20 13:19 UTCGHSA enrichmentGHSA-hf57-cqmx-p4gr · GitHub severity CRITICAL
  16. 2026-10-19 16:33 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  17. 2026-10-19 11:55 UTCEG score recompute
  18. 2026-10-19 11:55 UTCGHSA enrichmentGHSA-hf57-cqmx-p4gr · GitHub severity CRITICAL
  19. 2026-10-18 16:33 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  20. 2026-10-18 09:59 UTCGHSA enrichmentGHSA-hf57-cqmx-p4gr · GitHub severity CRITICAL
  21. 2026-10-18 03:03 UTCEG score recompute
  22. 2026-10-17 16:35 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  23. 2026-10-17 08:35 UTCEG score recompute
  24. 2026-10-17 08:34 UTCGHSA enrichmentGHSA-hf57-cqmx-p4gr · GitHub severity CRITICAL
  25. 2026-10-16 16:44 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  26. 2026-10-16 07:11 UTCEG score recompute
  27. 2026-10-16 07:11 UTCGHSA enrichmentGHSA-hf57-cqmx-p4gr · GitHub severity CRITICAL
  28. 2026-10-15 16:33 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  29. 2026-10-15 05:48 UTCEG score recompute
  30. 2026-10-15 05:48 UTCGHSA enrichmentGHSA-hf57-cqmx-p4gr · GitHub severity CRITICAL
  31. 2026-10-14 16:34 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  32. 2026-10-14 01:26 UTCEG score recompute
  33. 2026-10-14 01:25 UTCGHSA enrichmentGHSA-hf57-cqmx-p4gr · GitHub severity CRITICAL
  34. 2026-10-13 16:35 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  35. 2026-10-12 21:37 UTCEG score recompute
  36. 2026-10-12 21:37 UTCGHSA enrichmentGHSA-hf57-cqmx-p4gr · GitHub severity CRITICAL
  37. 2026-10-12 16:35 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  38. 2026-10-12 14:49 UTCEG score recompute
  39. 2026-10-11 21:48 UTCGHSA enrichmentGHSA-hf57-cqmx-p4gr · GitHub severity CRITICAL
  40. 2026-10-11 19:15 UTCEG score recompute
  41. 2026-10-11 16:32 UTCEG score recompute
  42. 2026-10-11 16:02 UTCEG score recompute
  43. 2026-10-11 16:01 UTCGHSA enrichmentGHSA-hf57-cqmx-p4gr · GitHub severity CRITICAL
  44. 2026-10-11 13:49 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  45. 2026-10-11 13:49 UTCEG score recompute
  46. 2026-10-11 11:44 UTCEG score recompute
  47. 2026-10-11 11:44 UTCGHSA enrichmentGHSA-hf57-cqmx-p4gr · GitHub severity CRITICAL
  48. 2026-10-11 07:01 UTCGHSA enrichmentGHSA-hf57-cqmx-p4gr · GitHub severity CRITICAL
  49. 2026-10-10 23:16 UTCEG score recompute
  50. 2026-10-10 23:15 UTCGHSA enrichmentGHSA-hf57-cqmx-p4gr · GitHub severity CRITICAL
  51. 2026-10-10 20:00 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  52. 2026-10-10 17:19 UTCGHSA enrichmentGHSA-hf57-cqmx-p4gr · GitHub severity CRITICAL
  53. 2026-10-10 13:02 UTCGHSA enrichmentGHSA-hf57-cqmx-p4gr · GitHub severity CRITICAL
  54. 2026-10-10 08:44 UTCGHSA enrichmentGHSA-hf57-cqmx-p4gr · GitHub severity CRITICAL
  55. 2026-10-10 04:25 UTCGHSA enrichmentGHSA-hf57-cqmx-p4gr · GitHub severity CRITICAL
  56. 2026-10-10 00:05 UTCEG score recompute
  57. 2026-10-10 00:05 UTCGHSA enrichmentGHSA-hf57-cqmx-p4gr · GitHub severity CRITICAL
  58. 2026-10-09 20:07 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  59. 2026-10-09 19:47 UTCGHSA enrichmentGHSA-hf57-cqmx-p4gr · GitHub severity CRITICAL
  60. 2026-10-09 08:18 UTCGHSA enrichmentGHSA-hf57-cqmx-p4gr · GitHub severity CRITICAL
  61. 2026-10-09 04:01 UTCGHSA enrichmentGHSA-hf57-cqmx-p4gr · GitHub severity CRITICAL
  62. 2026-10-08 23:44 UTCEG score recompute
  63. 2026-10-08 23:44 UTCGHSA enrichmentGHSA-hf57-cqmx-p4gr · GitHub severity CRITICAL
  64. 2026-10-08 17:13 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  65. 2026-10-08 08:44 UTCGHSA enrichmentGHSA-hf57-cqmx-p4gr · GitHub severity CRITICAL
  66. 2026-10-08 04:27 UTCGHSA enrichmentGHSA-hf57-cqmx-p4gr · GitHub severity CRITICAL
  67. 2026-10-08 00:09 UTCEG score recompute
  68. 2026-10-08 00:09 UTCGHSA enrichmentGHSA-hf57-cqmx-p4gr · GitHub severity CRITICAL
  69. 2026-10-07 23:48 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  70. 2026-10-07 19:52 UTCGHSA enrichmentGHSA-hf57-cqmx-p4gr · GitHub severity CRITICAL
  71. 2026-10-07 12:19 UTCGHSA enrichmentGHSA-hf57-cqmx-p4gr · GitHub severity CRITICAL
  72. 2026-10-07 07:59 UTCGHSA enrichmentGHSA-hf57-cqmx-p4gr · GitHub severity CRITICAL
  73. 2026-10-07 03:42 UTCGHSA enrichmentGHSA-hf57-cqmx-p4gr · GitHub severity CRITICAL
  74. 2026-10-06 23:09 UTCGHSA enrichmentGHSA-hf57-cqmx-p4gr · GitHub severity CRITICAL
  75. 2026-10-06 18:52 UTCEG score recompute

Public detection templates

(1 reference)

A public Nuclei detection template is referenced for this CVE. A detection template checks whether a system is affected; it is not necessarily exploit code.

  • Nucleihttp/cves/2026/CVE-2026-88062.yaml
    Published Sep 15, 2026

    OmniRoute < 3.8.49 - Unauthenticated RCE

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-88062?
CVE-2026-88062 is a critical-severity vulnerability; its CVE record was published on September 10, 2026. OmniRoute is an open-source AI gateway providing a single endpoint for multiple model providers. In 3.8.49 and earlier, the OmniRoute POST /api/acp/agents custom ACP agent endpoint accepted attacker-controlled binary and versionCommand values and used only a self-consistency check before…
When was the CVE record for CVE-2026-88062 published?
The CVE record for CVE-2026-88062 was published on September 10, 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 30, 2026; the record at its source may have been updated since.
Is CVE-2026-88062 actively exploited?
CVE-2026-88062 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.4% probability of exploitation in the next 30 days (72nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-88062?
CVE-2026-88062 has a CVSS base score of 9.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-88062?
No fix for CVE-2026-88062 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-88062 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-88062

Explore →

Is Your Infrastructure Affected by CVE-2026-88062?

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

Book a Demo →Browse All CVEs