OpenClaw CLI versions up to 2026.3.1 contain an authentication bypass vulnerability in the plugin route `/api/channels/*` due to a mismatch in path canonicalization depth. This allows specially encoded alternate-path requests to evade authentication checks while still resolving to protected routes. The issue is fixed in version 2026.3.2 with improved canonicalization and stricter auth enforcement.
OpenClaw CLI versions prior to 2026.2.25 have a vulnerability in Slack interactive callbacks where sender authorization checks can be bypassed in shared workspace deployments. This allows unauthorized workspace members to enqueue system-event text into active sessions. The issue does not grant unauthenticated access, cross-gateway isolation bypass, or host-level privilege escalation. A patch is planned in version 2026.2.25.
An experimental tool in OpenClaw CLI called apply_patch could bypass workspace-only checks in certain sandbox configurations. This issue only affects opt-in sandbox setups with specific flags enabled and does not impact default installations where sandbox mode and the experimental tool are disabled. The vulnerability was fixed in OpenClaw CLI version 2026.2.23.
OpenClaw CLI versions up to 2026.2.23 have a vulnerability in the safeBins allowlist policy where static default trusted directories include writable package-manager paths like /opt/homebrew/bin and /usr/local/bin. An attacker with write access to these directories can place a malicious binary with the same name as a trusted executable (e.g., jq), causing OpenClaw to execute the attacker-controlled binary. This allows command execution within the OpenClaw runtime context. The issue is fixed in version 2026.2.24 by restricting trusted directories to immutable system paths and requiring explicit opt-in for user-managed paths.
OpenClaw CLI versions up to 2026.3.1 have a vulnerability in webhook handlers for BlueBubbles and Google Chat where request bodies are parsed before authentication. This allows unauthenticated attackers to send slow or oversized request bodies, causing a denial of service by tying up parser resources. The issue is fixed in version 2026.3.2 by enforcing authentication before body parsing and adding strict limits on request processing time and size.
OpenClaw CLI versions up to 2026.2.24 contain a vulnerability in the gateway agents.files.get and agents.files.set methods that allows symlink traversal. This flaw permits reading and writing files outside the intended workspace by following symlinks, potentially enabling arbitrary host file access within the gateway process permissions. The vulnerability is patched in version 2026.2.25, which enforces path containment and rejects out-of-workspace symlink targets.
OpenClaw CLI versions up to 2026.2.25 are vulnerable to a metadata spoofing issue during node reconnection. An attacker with an already paired node identity can spoof platform and deviceFamily metadata to bypass platform-based node command policies. This allows unauthorized access to commands restricted by the original platform. The vulnerability is fixed in version 2026.2.26 by signing and verifying the platform metadata in the device-auth payload and rejecting mismatched reconnect metadata.
OpenClaw CLI versions from 2026.1.21 up to but not including 2026.2.18 contain a vulnerability in the tools.exec.safeBins allowlist mechanism. The vulnerability allows an attacker who can influence the PATH environment before the gateway process starts to execute trojan binaries named as allowed executables, bypassing the allowlist checks. This issue is rated medium severity due to the prerequisite of controlling the gateway launch environment. The vulnerability is fixed in version 2026.2.19 by enforcing that allowed executables must reside in trusted system directories.
OpenClaw CLI on macOS has a vulnerability in its optional exec-approval allowlist mode where basename-only entries are treated as trusted commands. This allows a local binary with the same name as an allowed command to execute without approval under certain security settings. The default security posture is not affected. A patch is planned in version 2026.2.22 to enforce path-only allowlist matching and remove basename fallback.
CVE-2026-32018 affects the openclaw-cli package, where concurrent operations on the sandbox registry can cause race conditions leading to lost updates or resurrection of removed entries. This occurs due to read-modify-write registry writes without proper locking, causing stale snapshots and overwrites. The issue impacts sandbox state consistency and related commands such as sandbox list, prune, and recreate. Versions up to 2026.2.17 are affected, with a fix available in version 2026.2.18.
OpenClaw CLI's Control UI static file handler improperly followed symbolic links, allowing an attacker to read files outside the intended root directory. This vulnerability is a path traversal issue caused by insufficient validation of symlinked asset paths. The flaw affects versions up to and including 2026.2.21-2 and is fixed in version 2026.2.22. The impact is primarily confidentiality loss due to out-of-root file reads. The severity is rated low in trusted environments but could be higher in shared or less controlled setups. A patch is available and enforces realpath containment to prevent directory traversal via symlinks.
OpenClaw CLI versions up to 2026.2.21-2 have a vulnerability in the Feishu allowlist authorization mechanism where an attacker can bypass authorization by exploiting display-name collisions. The allowlist is intended to match sender IDs, but the system incorrectly accepted mutable display names, allowing unauthorized senders to be authorized if their display name matched an allowlisted ID. This issue is fixed in version 2026.2.22 and later by enforcing strict ID-only matching and normalizing ID prefixes.
OpenClaw CLI versions from 2026.1.29 up to but not including 2026.2.24 contain a vulnerability in the system.run allowlist mode. A mismatch in dispatch-wrapper depth parsing allows nested transparent dispatch wrappers to bypass shell-wrapper approval gating, enabling execution without the expected approval prompt. This issue is rated high severity with a CVSS score of 8.8. The vulnerability is patched in version 2026.2.24.
OpenClaw CLI versions up to 2026.2.21 and certain prereleases contain a symlink traversal vulnerability in avatar handling. This flaw allows local files outside the intended workspace to be read via avatar response surfaces. The vulnerability impacts confidentiality by exposing local files accessible to the OpenClaw process. A fix is planned in version 2026.2.22, which enforces strict symlink and file identity checks to prevent traversal.
CVE-2026-32025 is a vulnerability in OpenClaw CLI versions before 2026.2.25 that allows a local browser-origin WebSocket authentication bypass on loopback deployments using password authentication. An attacker who convinces a user to open a malicious webpage can attempt to brute-force the gateway password without throttling, potentially gaining authenticated operator access. This issue is limited to local loopback access and requires a guessable password. The vulnerability is patched in version 2026.2.25.
A vulnerability in openclaw-cli versions from 2026.1.29 up to but not including 2026.2.26 allows DM pairing-store identities to bypass group allowlist authorization checks. This flaw enables a sender authorized via direct message pairing to satisfy group sender allowlist requirements without explicit inclusion in the group allowlist, causing an authorization boundary violation between DM pairing and group allowlists. The issue is fixed in version 2026.2.26.
OpenClaw CLI versions up to 2026.2.17 are vulnerable to sensitive file disclosure via the stageSandboxMedia function when iMessage remote attachment fetching is enabled. The vulnerability allows arbitrary absolute paths to be copied from a remote host, potentially exposing files outside expected attachment directories. This can lead to confidentiality breaches if an attacker can manipulate attachment path metadata. A fix is pending in the next release with remote attachment path validation. The issue is rated with a CVSS score of 7.5 (high severity).
OpenClaw CLI versions from 2026.1.29 up to but not including 2026.2.26 contain an authentication bypass vulnerability in the gateway authentication for plugin channel HTTP routes. This occurs due to a mismatch in path canonicalization between the gateway guard and the plugin handler routing, allowing unauthorized access to plugin channel APIs. The vulnerability is identified as CVE-2026-32031 and has a moderate severity rating.
OpenClaw CLI versions up to 2026.2.21-2 contain a vulnerability where the shell environment fallback trusts an unvalidated SHELL path from the host environment. This allows an attacker who can control the local environment or startup environment to influence which shell executable is invoked, potentially leading to high impact compromise. The vulnerability is not remotely exploitable without prior local environment compromise. A patch is available in version 2026.2.22 that validates the SHELL path against trusted locations and falls back safely to /bin/sh.
OpenClaw CLI versions up to 2026.3.1 have an authorization flaw in the Discord voice transcript handling where the owner-flag (senderIsOwner) is omitted, causing owner-only tools to be accessible to non-owner voice participants in the same channel. This issue arises because the agentCommand function defaults missing senderIsOwner to true, exposing privileged tools like gateway and cron. The vulnerability primarily affects mixed-trust deployments, which are outside the recommended use case of a single trusted operator. A fix is available in version 2026.3.2.