CVE-2026-88062

9.5

diegosouzapw · OmniRoute

OmniRoute contains a code injection vulnerability in the /api/acp/agents endpoint allowing unauthenticated remote attackers to execute arbitrary code via malicious interpreter evaluation arguments.

Executive summary

A critical code injection vulnerability in OmniRoute allows unauthenticated remote attackers to achieve full system compromise, necessitating immediate defensive action.

Vulnerability

The application fails to properly sanitize input in the /api/acp/agents endpoint, allowing attackers to pass arbitrary interpreter evaluation arguments to a system call. The vulnerability is further exacerbated by a flawed authentication check that permits anonymous access when the requireLogin configuration is set to false.

Business impact

Successful exploitation of this flaw allows an unauthenticated remote attacker to execute arbitrary commands within the server container, leading to a total loss of confidentiality, integrity, and availability. Given the CVSS score of 9.5, this vulnerability represents a critical risk that could lead to full system takeover, unauthorized data access, and potential lateral movement into backend AI model infrastructures.

Remediation

Immediate Action: As no official patch is currently available, administrators should immediately disable the OmniRoute service or restrict access to the /api/acp/agents endpoint via network-level controls.

Proactive Monitoring: Monitor server logs for suspicious POST requests to /api/acp/agents containing unusual binary or versionCommand parameters.

Compensating Controls: Implement a Web Application Firewall (WAF) rule to block requests to the /api/acp/ agents path and inspect incoming traffic for shell metacharacters or unexpected interpreter arguments.

Exploitation status

Public Exploit Available: Unknown

Analyst recommendation

This vulnerability is of the highest severity and requires urgent attention due to the potential for unauthenticated remote code execution. Administrators must isolate affected instances from public networks and monitor for unauthorized access until the vendor releases a secure version that implements proper input validation and mandatory authentication.

History

  1. Disclosed CVE record published
  2. Collected by CVE Brief via github
  3. Analyst report written
  4. Published in the daily brief critical section

Sources