# CVE-2026-88062: OmniRoute ACP Custom-Agent Remote Code Execution (RCE)

> Remote attackers can execute arbitrary code on OmniRoute servers by exploiting command injection in the custom agent endpoint when authentication is disabled or during bootstrap.

- **Severity:** Critical 9.5 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Sep 2026
- **Updated:** 11 Sep 2026
- **Also known as:** GHSA-hf57-cqmx-p4gr

## What is CVE-2026-88062?

CVE-2026-88062 is a critical command injection vulnerability in diegosouzapw OmniRoute, published on 10 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-88062?

2 open source packages ship an affected version, including omniroute.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `omniroute` | npm | All versions to 3.8.50 | None |
| `omniroute` | npm | All versions to 3.8.50 | None |

## How do I fix CVE-2026-88062?

No fix has been published for CVE-2026-88062 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-88062 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-88062 exists.

Public exploit code:

- OmniRoute < 3.8.49 - Unauthenticated RCE (nuclei): http/cves/2026/CVE-2026-88062.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-88062 and fix it if it is affected.

What it is: CVE-2026-88062 is a critical command injection vulnerability in diegosouzapw OmniRoute, published on 10 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-88062 exists.

Affected packages and fixed versions:
- omniroute (npm): affected all versions up to 3.8.50; no fix listed
- omniroute (npm): affected all versions up to 3.8.50; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-88062/ (Markdown: https://insights.sbomify.com/CVE-2026-88062/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-88062
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-88062
- OSV: https://osv.dev/vulnerability/CVE-2026-88062

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-88062/
Summaries are generated and may contain mistakes; the official description above is the record.