Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-88062 – Unauthenticated Remote Code Execution – OmniRoute < 3.8.49

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-88062 is a critical remote code execution vulnerability in OmniRoute, an open-source AI gateway that provides a single endpoint for multiple LLM providers. The flaw combines a code injection weakness (CWE-94) in the ACP custom-agent registration endpoint with a missing authentication check (CWE-306), letting an attacker who can reach the endpoint execute arbitrary commands inside the OmniRoute container. The issue carries a CVSS v4.0 base score of 9.5 (Critical).

Technical details

  • The POST /api/acp/agents endpoint lets callers register a custom ACP agent by supplying binary and versionCommand values.
  • Validation only checks that the first token of versionCommand matches the supplied binary value; since both fields are attacker-controlled, this check is trivially satisfied.
  • Registration triggers immediate version-probe logic (refreshAgentCache → resolveVersionProbe) that runs execFileSync(probe.command, probe.args, ...) using the attacker-supplied command.
  • The tokenizeVersionCommand function and DISALLOWED_VERSION_COMMAND_CHARS filter block a limited set of shell metacharacters but do not prevent interpreter evaluation flags (e.g., node -e "<code>"), allowing arbitrary code execution.
  • Authentication for the endpoint is governed by isAuthenticated/isAuthRequired, which permits anonymous requests when requireLogin=false or during initial bootstrap before a management password is configured; /api/acp/ is also absent from the LOCAL_ONLY_API_PREFIXES and SPAWN_CAPABLE_PREFIXES protective lists.
  • Attack vector is network-based, requires no user interaction, and (under the vulnerable configuration) no privileges — a single crafted HTTP request achieves code execution inside the container.
  • With requireLogin=true and a management password configured, exploitation requires valid management credentials or API keys.

Affected software

  • OmniRoute versions prior to 3.8.49 (< 3.8.49)

Severity

  • CVSS v4.0 Base Score: 9.5 (Critical)
  • Vector: 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

Mitigation and recommended actions

  • Immediate: Upgrade OmniRoute to version 3.8.49 or later, which addresses the validation and authentication gaps in the ACP agent endpoint.
  • If patching is not immediately possible:
    • Ensure requireLogin is enabled and a management password is configured before exposing the instance to any network.
    • Do not expose the /api/acp/agents endpoint (or the OmniRoute management interface generally) to untrusted or public networks; restrict access to trusted internal hosts only.
    • Monitor for unexpected agent registrations or unusual process execution originating from the OmniRoute container.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge