diegosouzapw OmniRoute up to 3.8.49 ACP Agent /api/acp/agents tokenizeVersionCommand versionCommand os command injection

Summaryinfo

A vulnerability has been found in diegosouzapw OmniRoute up to 3.8.49 and classified as critical. Impacted is the function tokenizeVersionCommand of the file /api/acp/agents of the component ACP Agent. The manipulation of the argument versionCommand leads to os command injection. This vulnerability is traded as CVE-2026-88062. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability was found in diegosouzapw OmniRoute up to 3.8.49. It has been rated as critical. This issue affects the function tokenizeVersionCommand of the file /api/acp/agents of the component ACP Agent. The manipulation of the argument versionCommand with an unknown input leads to a os command injection vulnerability. Using CWE to declare the problem leads to CWE-78. The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

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.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-88062 since 09/09/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 09/10/2026). MITRE ATT&CK project uses the attack technique T1202 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• diegosouzapw

Name

• OmniRoute

Version

• 3.8.0
• 3.8.1
• 3.8.2
• 3.8.3
• 3.8.4
• 3.8.5
• 3.8.6
• 3.8.7
• 3.8.8
• 3.8.9
• 3.8.10
• 3.8.11
• 3.8.12
• 3.8.13
• 3.8.14
• 3.8.15
• 3.8.16
• 3.8.17
• 3.8.18
• 3.8.19
• 3.8.20
• 3.8.21
• 3.8.22
• 3.8.23
• 3.8.24
• 3.8.25
• 3.8.26
• 3.8.27
• 3.8.28
• 3.8.29
• 3.8.30
• 3.8.31
• 3.8.32
• 3.8.33
• 3.8.34
• 3.8.35
• 3.8.36
• 3.8.37
• 3.8.38
• 3.8.39
• 3.8.40
• 3.8.41
• 3.8.42
• 3.8.43
• 3.8.44
• 3.8.45
• 3.8.46
• 3.8.47
• 3.8.48
• 3.8.49

Website

• Product: https://github.com/diegosouzapw/OmniRoute/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion