A signature verification bypass vulnerability exists in the OpenClaw CLI's Twilio voice-call webhook extension when the ngrok free-tier loopback compatibility option is enabled. This optional voice-call extension is disabled by default, and the bypass only occurs if the specific configuration option 'tunnel.allowNgrokFreeTierLoopbackBypass' is explicitly enabled. Exploitation requires the webhook endpoint to be publicly reachable, typically via a public ngrok URL used during development. An attacker could send forged webhook requests without a valid Twilio signature, potentially causing unauthorized webhook event handling and request flooding. The issue affects OpenClaw CLI versions from 2026.1.29 up to but not including 2026.2.14. A fix is available in version 2026.2.14, which removes the signature verification bypass while preserving trusted forwarded headers for correct signature validation.
OpenClaw CLI versions up to 2026.2.21-2 have a vulnerability in the allow-always wrapper persistence mechanism that can bypass future command approvals in allowlist mode. This flaw allows an attacker to execute commands without re-approval by exploiting persistent wrapper-level allowlist entries. The issue affects execution approval persistence flows and is fixed in version 2026.2.22. Until patched, stricter execution policies can mitigate the risk.
OpenClaw CLI version 2026.3.1 contains a vulnerability in its node system.run approval wrapper that causes a semantic drift in command execution. The wrapper rewrites the command arguments in a way that the approved command text shown to the operator can differ from the actual executed command, potentially running unintended local scripts. This occurs when the wrapper argv is rewritten, causing the shell to interpret an extra positional argument as a script path. The issue is fixed in version 2026.3.2.
OpenClaw CLI versions prior to 2026.2.14 have a denial of service vulnerability caused by unbounded memory allocation when fetching URL-backed media. The issue arises because the entire response payload is buffered in memory before enforcing the maximum allowed size, allowing attackers to exhaust memory with oversized responses. This can lead to availability loss. A patch is available in version 2026.2.14.
OpenClaw CLI versions before 2026.2.14 are vulnerable to command hijacking due to unsafe PATH handling. This allows an attacker with certain access to cause OpenClaw to execute unintended binaries by manipulating the PATH environment variable. The vulnerability arises in two scenarios: one involving remote node-host PATH overrides and another involving local project directory PATH bootstrapping. The issue is mitigated in version 2026.2.14 and later by disabling project-local PATH bootstrapping by default and ignoring request-scoped PATH overrides on the node host.
OpenClaw CLI versions before 2026.2.14 contain a Local File Inclusion (LFI) vulnerability in the BlueBubbles media path handling. This flaw allows an attacker to specify arbitrary local filesystem paths via the mediaPath parameter, enabling reading and exfiltration of local files accessible to the OpenClaw process. The vulnerability is fixed in version 2026.2.14 by enforcing explicit allowlisting of trusted directories and canonical path containment checks.
OpenClaw CLI versions before 2026.2.14 have a denial of service vulnerability caused by decoding large base64 media inputs into buffers before enforcing size limits. This can lead to excessive memory allocation and memory pressure, resulting in service disruption. The vulnerability is primarily a local or authorized DoS risk when the gateway is bound to loopback with authentication. Exposure to untrusted networks or weakened authentication increases the risk severity. A fix is planned in version 2026.2.14.
OpenClaw CLI versions before 2026.2.12 have a webhook authentication bypass vulnerability in the BlueBubbles webhook handler when the gateway is behind a reverse proxy. The handler incorrectly treats requests from loopback addresses as authenticated, allowing attackers who can reach the proxy endpoint to inject unauthorized BlueBubbles events. This affects deployments exposing the BlueBubbles webhook endpoint through a reverse proxy. A patch is available in version 2026.2.12 that removes this bypass and requires the webhook secret for authentication.
OpenClaw CLI versions up to 2026.2.26 have a server-side request forgery (SSRF) vulnerability in the Gemini web_search citation redirect feature. This vulnerability allows an attacker who can control citation redirect targets to cause the OpenClaw host to make requests to internal or loopback network addresses. The issue arises because the citation redirect resolution used a private-network-allowing SSRF policy. The vulnerability is fixed in version 2026.3.1 by enforcing a strict SSRF policy that blocks localhost and private/internal redirect targets.
The OpenClaw CLI contained a vulnerability in the stageSandboxMedia function that allowed destination symlink traversal during media staging. This flaw could enable overwriting files outside the intended sandbox workspace by following symlinks in the destination path. The issue affected openclaw versions up to 2026.3.1 and was fixed in version 2026.3.2 by enforcing safe write primitives that prevent symlink traversal escapes.
OpenClaw CLI versions up to 2026.2.25 contain an authorization bypass vulnerability in Signal group allowlist enforcement. When groupPolicy is set to allowlist, sender identities approved via direct message (DM) pairing-store could improperly bypass group allowlist checks. This occurs because DM pairing approvals leak into group allowlist evaluation, weakening the authorization boundary between DM pairing and group membership controls. The issue is fixed in version 2026.2.26 by isolating DM pairing-store entries to DM-only and enforcing explicit group allowlist boundaries.
A parsing mismatch vulnerability in the beta macOS companion app of OpenClaw CLI allows shell-chain payloads to bypass allowlist checks in the system.run command under specific conditions. This requires an authenticated caller with operator.write permission, a paired macOS beta node host, and exec approvals configured to security=allowlist with ask=on-miss. Default installs are not affected. The issue is fixed in the planned next release 2026.2.22.
OpenClaw CLI versions up to 2026.2.17 have a local command injection vulnerability in Windows Scheduled Task script generation due to unsafe handling of cmd arguments in generated gateway.cmd files. This allows cmd metacharacter-only values to be emitted without proper quoting or escaping, potentially causing unintended command execution when the scheduled task runs. The issue is fixed in version 2026.2.19 and later.
OpenClaw CLI on Windows contains a command injection vulnerability in a fallback path where the Lobster extension retries certain spawn failures using a shell. This fallback interprets tool-provided arguments via cmd.exe, potentially allowing command injection. The issue affects versions from 2026.1.21 through 2026.2.17 and is fixed in version 2026.2.19 by removing the shell fallback and enforcing safer execution methods.
OpenClaw CLI versions up to 2026.2.26 have a vulnerability where system.run approvals do not bind the executable identity for commands resolved via PATH tokens. This allows a previously approved action to execute a different binary if the PATH resolution changes after approval. The issue is fixed in version 2026.3.1 by requiring immutable systemRunPlan data and pinning path-token commands to their canonical executable identity.
OpenClaw CLI versions 2026.2.22 and 2026.2.23 contain an authorization flaw in the synology-chat channel plugin. When the dmPolicy is set to allowlist but the allowedUserIds list is empty or unset, unauthorized Synology senders can dispatch agents. This issue requires specific plugin setup and sender access, leading to a medium severity classification. The vulnerability is fixed in version 2026.2.24.
Openclaw CLI versions from 2026.2.26 up to but not including 2026.3.1 on Windows have a vulnerability in the ACPX wrapper resolution for .cmd/.bat files. The fallback to shell execution allowed the current working directory (cwd) to influence execution behavior, potentially compromising command execution integrity. This issue is fixed in version 2026.3.1 by enforcing explicit PATH/PATHEXT entrypoint resolution and strict fail-closed handling for unresolvable wrappers.
OpenClaw CLI versions up to 2026.2.17 contain a command injection vulnerability in the Lobster extension tool execution on Windows. The vulnerability arises from a fallback to Windows shell execution with shell metacharacter interpretation after subprocess spawn failures. This allows command injection via crafted command arguments. The issue is fixed in version 2026.2.19 by removing the shell fallback and using explicit executable/script argument execution.
OpenClaw CLI versions up to 2026.2.21-2 allow clients authenticated with a shared gateway token to connect as role=node without device identity verification. This bypass enables unauthorized injection of node.event messages, triggering agent request and voice transcript flows. The vulnerability is fixed in version 2026.2.22, which enforces device identity for role=node connections even when shared-token authentication succeeds.
OpenClaw CLI's sandboxed image tool bypasses the workspace-only file access restriction, allowing it to read and exfiltrate mounted images outside the designated workspace. This vulnerability affects versions prior to 2026.2.23 and was fixed by enforcing workspace-only constraints on the image tool's path resolution. The issue results in a sandbox boundary bypass with confidentiality impact but does not affect integrity or availability.