OpenClaw CLI versions from 2026.1.29 up to but not including 2026.3.24 contain an authorization flaw in the internal `/allowlist` chat commands. These commands allow an authenticated internal Gateway caller with `operator.write` scope to perform mutating actions that should require `operator.admin` scope. This missing authorization check permits persistent changes to configuration and pairing-store allowlist entries without proper admin privileges. The issue was fixed in OpenClaw 2026.3.24.
OpenClaw CLI versions prior to 2026.2.13 have an issue where inter-session messages sent via sessions_send are stored as user role messages without provenance metadata. This causes confusion between external user input and internal inter-session instructions, potentially leading to unintended privileged behavior in workflows that trust the user role as an authority signal. The vulnerability is fixed in version 2026.2.13 by adding explicit input provenance metadata to distinguish inter-session messages from genuine user input.
Several Dockerfiles used for end-to-end (E2E) testing and installation in the OpenClaw CLI project run all processes as root due to the absence of a USER directive. This allows processes inside these containers to run with uid 0, increasing the risk of container breakout if compromised. While some Dockerfiles (sandbox and sandbox-browser) have been partially fixed by adding a non-root user, the E2E/test Dockerfiles remain unpatched. The base images used default to root, and the affected Dockerfiles include scripts/e2e/Dockerfile, scripts/e2e/Dockerfile.qr-import, and scripts/docker/install-sh-e2e/Dockerfile. Remediation involves adding a USER directive to run processes as a non-root user.
OpenClaw CLI versions up to 2026.2.19-2 are affected by a startup-file injection vulnerability involving the BASH_ENV and ENV environment variables. This flaw allows unintended shell command execution when attacker-controlled environment values are inherited by spawned shell commands. The vulnerability requires local or privileged access to influence environment inputs and cannot be triggered remotely without authentication. A fix has been committed and will be released in version 2026.2.21.
OpenClaw CLI versions up to 2026.3.28 are affected by an environment variable injection vulnerability in the Host-Exec feature. This allows environment variables controlled by the user to influence interpreters, shells, or build tools during host execution. The vulnerability is scoped to the OpenClaw trust model and does not assume multi-tenant service boundaries. A fix is available in version 2026.4.8.
A time-of-check to time-of-use (TOCTOU) symlink race condition exists in OpenClaw CLI's writeFileWithinRoot function. This vulnerability allows an attacker to manipulate a symlink path between resolution and file write operations, potentially causing file creation or truncation outside the intended root directory. The issue affects versions up to 2026.2.26 and is fixed in version 2026.3.1 by changing the file write flow to include post-open identity and boundary checks and exclusive file creation semantics.
A sandbox path validation bypass vulnerability in the openclaw CLI allows unauthorized reading of host files outside the intended sandboxRoot. This occurs when the fallback temporary directory used by openclaw is a symlink alias, enabling media paths under this fallback root to escape sandbox confinement. The issue affects openclaw versions up to 2026.2.24 and is fixed in version 2026.2.25.
OpenClaw CLI versions prior to 2026.6.5 have a vulnerability where MCP SSE redirects could forward Authorization headers improperly. This flaw allows a lower-trust caller or certain input paths to execute or persist actions beyond their intended authorization scope. The issue affects configurations where the vulnerable feature is enabled and reachable. The vulnerability does not alter the trusted-operator model of OpenClaw but can lead to unauthorized action execution if exploited. A patch is available in version 2026.6.5. Until upgrading, restricting the feature to trusted operators or disabling it is recommended.
OpenClaw CLI versions before 2026.5.19 contain a vulnerability where message read actions can bypass channel allowlist checks. This allows lower-trust callers with access to these actions to request messages from channels they should not normally access. The impact depends on the operator's configuration and whether untrusted inputs can reach the vulnerable path. The issue does not affect the trusted-operator model but can expose sensitive messages if the feature is enabled and reachable. A fix is available in version 2026.5.19.
OpenClaw CLI had a vulnerability where certain browser control interactions could bypass private-network navigation checks, allowing authenticated users with browser evaluation capabilities to read content from private or loopback URLs. This issue affected versions prior to 2026.5.18 and was fixed in that release. The vulnerability requires authenticated access and does not grant unauthorized access to OpenClaw itself. Mitigation involves upgrading to version 2026.5.18 or later and restricting browser control access to trusted operators before patching.
OpenClaw CLI versions prior to 2026.5.18 contain a vulnerability where marketplace runtime extension metadata can redirect runtime loading to unscanned payloads. This allows a package selected by a trusted operator to load plugin code outside the reviewed package entry points. The vulnerability depends on the operator's configuration and whether lower-trust input can reach the affected feature. A fix is available in version 2026.5.18.
A vulnerability in OpenClaw CLI's Control UI allows an attacker with network access to spoof locality information during pairing, potentially obtaining a durable admin device token. This issue affects LAN/shared-token deployments where locality signals are trusted for pairing decisions. The vulnerability enables persistence of admin access even after shared tokens are rotated unless the paired device is removed. It is not exploitable remotely without prior network/authentication access. A fix is available in version 2026.5.22.
OpenClaw CLI versions prior to 2026.5.20 contain a vulnerability where hook-triggered runs using a configured hook token could escalate privileges by selecting a CLI backend with owner-level MCP tool authority. This affects deployments with hooks enabled and accessible hook tokens, potentially allowing unauthorized access to owner-only MCP tools. The issue is fixed in version 2026.5.20.
A vulnerability in openclaw-cli allows a workspace .env file to override the Homebrew executable selection during skill install flows. This could cause an unintended Homebrew-compatible executable to run if the feature is enabled and reachable. The issue affects versions prior to 2026.5.27. The vulnerability relies on trusted operators opening repositories with a crafted .env file. The impact depends on the operator's configuration and the trust level of inputs reaching the affected path. A patch is available in version 2026.5.27. Until patched, it is recommended to avoid running skill install flows from untrusted workspaces and to apply configuration hardening measures.
OpenClaw CLI versions prior to 2026.4.25 contain a vulnerability where fake package roots can influence memory-core artifact loading. This occurs because a local package root resolution path, influenced by workspace state, may select an unintended package root. The vulnerability affects configurations where the feature is enabled and reachable, potentially allowing loading of memory-core artifacts from unintended local locations. The impact depends on operator configuration and whether lower-trust input can reach the affected path. The vulnerability is patched starting from version 2026.4.25. Until patched, it is recommended to run memory-core flows only from trusted workspaces and apply general hardening such as narrowing allowlists and disabling the feature when not needed.
OpenClaw CLI has a vulnerability where the embedded runner policy can be confused by provider aliases. This means that requests using provider aliases might compare policy against an alias rather than the canonical provider identity, potentially allowing access to bundled tools outside the intended provider policy. The issue affects versions before 2026.4.25. The vulnerability has a low severity score and does not affect the trusted-operator model of OpenClaw. Mitigation includes avoiding provider alias routing for embedded runner tool policy until patched and applying general hardening measures.
OpenClaw CLI versions prior to 2026.5.18 contain a vulnerability where paired nodes can forge exec lifecycle events without sufficient provenance verification. This allows a malicious or compromised paired node to send crafted lifecycle events to the gateway, potentially causing the gateway to treat attacker-supplied data as legitimate exec lifecycle results. The vulnerability requires the attacker to already control a paired node connection and does not allow unauthenticated access to the gateway. The issue is resolved in version 2026.5.18.
OpenClaw CLI versions prior to 2026.5.12 contain a vulnerability where combined POSIX shell options can cause confusion during exec revalidation. This may lead to inline shell commands executing without proper allowlist approval. The issue affects configurations where the feature is enabled and reachable, potentially allowing unintended command execution depending on operator setup. The vulnerability does not alter the trusted-operator model of OpenClaw. A fix is available in version 2026.5.12.
A vulnerability in OpenClaw CLI's MCP loopback feature allows non-owner callers to bypass owner-only tool policies and before-tool-call hooks. This issue affects versions from 2026.1.29 up to but not including 2026.4.24. The impact depends on the operator's configuration and whether untrusted inputs can reach the affected loopback path. A patch is available to address this issue. Until patched, restricting MCP loopback access to trusted operators and narrowing allowlists is recommended.
OpenClaw CLI's Matrix allowFrom feature could bind to mutable display names, allowing a Matrix account that can change display name metadata to match a policy entry through mutable display metadata. This vulnerability affects versions prior to 2026.5.7 and could lead to unauthorized agent access intended for another Matrix identity. The issue does not alter OpenClaw's trusted-operator model but depends on operator configuration and input trust levels. A patch is available in version 2026.5.7.