CVE-2026-25157

Two related vulnerabilities existed in the macOS application's SSH remote connection handling (CommandResolver.swift):

Details

The sshNodeCommand function constructed a shell script without properly escaping the user-supplied project path in an error message. When the cd command failed, the unescaped path was interpolated directly into an echo statement, allowing arbitrary command execution on the remote SSH host.

The parseSSHTarget function did not validate that SSH target strings could not begin with a dash. An attacker-supplied target like -oProxyCommand=... would be interpreted as an SSH configuration flag rather than a hostname, allowing arbitrary command execution on the local machine.

An attacker who can influence a user's remote connection settings (via social engineering or malicious configuration) could achieve arbitrary code execution on either the user's local machine or their configured remote SSH host, depending on which input vector is exploited.

Affected component: macOS menubar application (Remote/SSH mode only)

Not affected: CLI (npm install openclaw), web gateway, iOS/Android apps, or users running in Local mode.

Untrusted input reaches a shell command, allowing arbitrary commands to run on the host. Typical impact: code execution in the application's environment.

CVE-2026-25157 has a CVSS score of 7.7 (High). The vector is requires local access, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2026.1.29); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-25157? CVE-2026-25157 is a high-severity OS command injection vulnerability in clawdbot (npm), affecting versions < 2026.1.29. It is fixed in 2026.1.29. Untrusted input reaches a shell command, allowing arbitrary commands to run on the host.
2. How severe is CVE-2026-25157? CVE-2026-25157 has a CVSS score of 7.7 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of clawdbot are affected by CVE-2026-25157? clawdbot (npm) versions < 2026.1.29 is affected.
4. Is there a fix for CVE-2026-25157? Yes. CVE-2026-25157 is fixed in 2026.1.29. Upgrade to this version or later.
5. Is CVE-2026-25157 exploitable, and should I be worried? Whether CVE-2026-25157 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-25157 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-25157? Upgrade clawdbot to 2026.1.29 or later.