Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.5amended

OmniRoute ACP Custom-Agent Remote Code Execution (RCE)

CVE-2026-88062GHSA-hf57-cqmx-p4gr

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm omniroute

    Affected
    <= 3.8.50
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
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 · score source
EPSS
  • CVE-2026-88062: 1.42% estimated exploitation activity in the next 30 days; percentile 72.94 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

2. Summary POST /api/acp/agents registers a custom ACP agent. The endpoint accepts user-controlled binary and versionCommand values. After saving the custom agent, the same request calls refreshAgentCache(), which triggers agent version detection. The version probe eventually runs: The only validation is resolveVersionProbe(binary, versionCommand, true), which checks that the first token of versionCommand matches the request-provided binary. Because binary is also attacker-controlled, an attacker can submit: This executes arbitrary Node.js code inside the server container, and that code can execute OS commands via childprocess.execSync(). When requireLogin=false, isAuthenticated() treats anonymous requests as authenticated. At the same time, /api/acp/ is not included in LOCALONLYAPIPREFIXES or SPAWNCAPABLEPREFIXES, so the endpoint is not blocked by the LOCALONLY policy before reaching the anonymous allow branch. As a result, a remote anonymous attacker can execute commands inside the…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 4 · amended ·

    Amended from ghsa record GHSA-hf57-cqmx-p4gr

  2. Revision 3 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 2 · amended ·

    Amended from osv record GHSA-hf57-cqmx-p4gr

  4. Revision 1 · created ·

    Published from ghsa record GHSA-hf57-cqmx-p4gr

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-88062

Advisory: OmniRoute ACP Custom-Agent Remote Code Execution (RCE)
IDs: CVE-2026-88062, GHSA-hf57-cqmx-p4gr
Record: https://patchnext.com/advisories/cve-2026-88062 (revision 4, source checked 26 Oct 2026, 13:02 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm omniroute: affected <= 3.8.50

## Suggested inspection (read-only)
- `npm ls omniroute --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on omniroute.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-hf57-cqmx-p4gr (GitHub-reviewed advisory GHSA-hf57-cqmx-p4gr lists affected ranges: npm omniroute >=0 <=3.8.50)
- Verified: https://osv.dev/vulnerability/GHSA-hf57-cqmx-p4gr (OSV record GHSA-hf57-cqmx-p4gr lists affected ranges: npm omniroute >=0 <=3.8.50)

Commands are suggestions: review each one before running it.

Loading voting…