Summary
OpenClaw macOS deep link confirmation truncation can conceal executed agent message
OpenClaw macOS desktop client registers the openclaw:// URL scheme. For openclaw://agent deep links without an unattended key, the app shows a confirmation dialog that previously displayed only the first 240 characters of the message, but executed the full message after the user clicked "Run".
At the time of writing, the OpenClaw macOS desktop client is still in beta.
An attacker could pad the message with whitespace to push a malicious payload outside the visible preview, increasing the chance a user approves a different message than the one that is actually executed.
Affected Versions
- OpenClaw macOS desktop client versions >= 2026.2.6 and <= 2026.2.13.
Fixed Versions
- 2026.2.14.
Mitigations
- Do not approve unexpected "Run OpenClaw agent?" prompts triggered while browsing untrusted sites.
- Use unattended deep links only with a valid
keyfor trusted personal automations.
Resolution
Unkeyed deep links now enforce a strict message length limit for confirmation and ignore delivery/routing knobs (deliver, to, channel) unless a valid unattended key is provided.
Fix commit: 28d9dd7a772501ccc3f71457b4adfee79084fe6f
Fix commit 28d9dd7a772501ccc3f71457b4adfee79084fe6f confirmed on main and in v2026.2.14. Upgrade to openclaw >= 2026.2.14.
Impact
If a user runs the deep link, the agent may perform actions that can lead to arbitrary command execution depending on the user's configured tool approvals/allowlists. This is a social-engineering mediated vulnerability: the confirmation prompt could be made to misrepresent the executed message.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
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. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-26320? CVE-2026-26320 is a high-severity security vulnerability in openclaw (npm), affecting versions >= 2026.2.6-0, < 2026.2.14. It is fixed in 2026.2.14.
- Which versions of openclaw are affected by CVE-2026-26320? openclaw (npm) versions >= 2026.2.6-0, < 2026.2.14 is affected.
- Is there a fix for CVE-2026-26320? Yes. CVE-2026-26320 is fixed in 2026.2.14. Upgrade to this version or later.
- Is CVE-2026-26320 exploitable, and should I be worried? Whether CVE-2026-26320 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
- What actually determines whether CVE-2026-26320 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.
- How do I fix CVE-2026-26320? Upgrade
openclawto 2026.2.14 or later.