A vulnerability in openclaw-cli's node host system.run handler allows bypassing allowlist enforcement and approval prompts due to a mismatch between rawCommand and command[]. This affects deployments using node host execution with allowlist-based exec policy and approval prompting on allowlist misses. An attacker invoking system.run can supply an allowlisted rawCommand but execute a different command[], bypassing security controls. The issue affects openclaw versions from 2026.1.29 up to but not including 2026.2.14. A patch is planned in version 2026.2.14 to enforce consistency between rawCommand and command[].
The OpenClaw CLI's skills.status method could leak sensitive configuration secrets to clients with operator.read permissions by exposing raw resolved config values. This vulnerability affects versions up to 2026.2.13 and was fixed in version 2026.2.14 by removing raw config values from the output and narrowing config requirements. The issue could expose secrets such as Discord bot tokens to unauthorized read-scoped clients.
OpenClaw CLI versions before 2026.2.14 allow unauthenticated discovery TXT records to influence routing and TLS pinning decisions. This vulnerability affects clients on shared or untrusted LANs where an attacker can advertise rogue services to redirect connections and override TLS pins. The impact is mainly on iOS and Android clients in alpha or testing phases, limiting exposure. A fix is planned in version 2026.2.14 that changes clients to prefer SRV and A/AAAA records over TXT records and requires explicit user confirmation for TLS pinning on mobile platforms.
A vulnerability in openclaw-cli allows iMessage group authorization under groupPolicy=allowlist to be satisfied by sender identities from the DM pairing store. This broadens trust from direct messages into group contexts, weakening boundary separation between DM pairing and group allowlist authorization. The issue affects openclaw versions from 2026.1.29 up to but not including 2026.2.14. A fix is available in later versions.
OpenClaw CLI versions prior to 2026.2.14 contain a path traversal vulnerability in the browser upload functionality that allows authenticated users to read arbitrary files on the Gateway host. This occurs because the server passes user-supplied file paths directly to Playwright's file input APIs without restricting them to a safe directory. Exploitation requires valid authentication and permission to use the browser tool, limiting exposure to authorized users. The vulnerability is fixed in version 2026.2.14 by restricting upload paths to a designated temporary directory and rejecting traversal sequences.
OpenClaw CLI versions from 2026.1.29 up to 2026.2.12 contain a path traversal vulnerability in the browser download functionality. This flaw allows authenticated users with CLI or gateway RPC token access to write files outside the intended temporary downloads directory. The vulnerability is fixed in version 2026.2.13 by restricting download paths to a designated directory.
OpenClaw CLI versions up to 2026.2.14 contain a configuration injection vulnerability that allows dangerous Docker options to be applied in the sandbox environment. This can enable container escape or unauthorized access to host data by mounting sensitive host paths, using host networking, or disabling security profiles. The issue is fixed in version 2026.2.15 by blocking unsafe Docker settings and validating configuration schemas.
OpenClaw CLI versions up to 2026.2.14 log Telegram bot tokens in error messages and stack traces without redaction, potentially exposing these tokens in logs, crash reports, CI outputs, or support bundles. This exposure allows attackers to impersonate the bot and gain unauthorized Bot API access. The issue is fixed in version 2026.2.15. Users should upgrade to this version and rotate any potentially exposed Telegram bot tokens.
OpenClaw CLI versions up to 2026.2.14 have a session visibility configuration issue in multi-user shared-agent deployments, potentially exposing session transcript content across peers. Additionally, Telegram webhook mode lacked fallback to per-account webhook secrets, risking secret misconfiguration. The vulnerability mainly affects less-trusted, multi-user environments, with limited impact in single-agent or trusted setups. A patch is planned in version 2026.2.15 to enforce session visibility scoping and fix Telegram webhook secret fallback.
OpenClaw CLI versions up to 2026.2.14 have a configuration integrity vulnerability where the sandbox configuration hash normalization incorrectly sorted primitive arrays, causing order-sensitive configuration changes to be ignored. This leads to stale sandbox containers being reused instead of recreated when array order changes. The issue is fixed in version 2026.2.15 by preserving array order during hash normalization.
A vulnerability in openclaw-cli versions up to 2026.2.14 allows the admin-only skills installation process to write files outside the intended sandbox directory due to insufficient validation of the target directory path. This could lead to unauthorized file writes outside the per-skill tools directory. A fix is planned for version 2026.2.15.
OpenClaw CLI versions up to 2026.3.2 have a vulnerability in the system.run dispatch-wrapper handling where shell-wrapper approval gating can be bypassed under specific conditions involving four transparent dispatch wrappers. This mismatch allows execution planning to unwrap through to the shell payload without triggering the expected approval in security=allowlist mode. The issue is fixed in version 2026.3.7 by aligning shell-wrapper classification with execution planning at the configured dispatch depth boundary.
Openclaw CLI versions up to 2026.2.17 have a vulnerability in Discord moderation action handling where sender identity is taken from untrusted request parameters instead of a trusted runtime context. This allows a non-admin user with the bot's guild permissions to spoof sender identity and request moderation actions such as timeout, kick, or ban. The issue is fixed in version 2026.2.18 by using a trusted sender context and adding permission checks.
The OpenClaw CLI's local skill packaging script previously followed symlinks when creating .skill archives, potentially including unintended local files outside the skill directory. This vulnerability is limited to local execution by skill authors packaging skills and does not affect remote or runtime components. The issue is fixed by rejecting symlinks during packaging in version 2026.2.18.
OpenClaw CLI versions before 2026.2.14 have a vulnerability in their process cleanup routine where the tool may kill unrelated processes on shared hosts due to unvalidated PID termination based on pattern matching. This occurs because the cleanup did not verify process ownership before sending SIGKILL signals. The issue is fixed in version 2026.2.14 by restricting termination to child processes owned by the current process and improving matching logic.
The Openclaw CLI npm package versions up to 2026.2.17 contain a server-side request forgery (SSRF) vulnerability in the cron webhook delivery mechanism. The vulnerability arises because the code uses fetch() directly without SSRF policy checks, allowing webhook targets to access internal or private endpoints. This issue was fixed in versions after 2026.2.17 with specific commits addressing the problem.
OpenClaw CLI versions before 2026.2.24 contain a vulnerability where message actions 'sendAttachment' and 'setGroupIcon' can hydrate media from local absolute paths if the 'sandboxRoot' is unset. This bypasses local media root checks and could allow reading arbitrary files accessible to the runtime user. The issue is fixed in version 2026.2.24 and later.
OpenClaw CLI versions up to 2026.2.23 contain a vulnerability in sandbox bind-source validation. The issue allows bypassing allowed-root and blocked-path checks by using a symlinked parent directory combined with a non-existent leaf path. This causes the sandbox boundary enforcement to be weakened, potentially allowing paths to resolve outside intended allowed roots. The vulnerability is fixed in version 2026.2.24 by improving canonicalization of paths during validation.
OpenClaw CLI's runtime `/debug set` override functionality accepted prototype-reserved keys such as `__proto__`, `constructor`, and `prototype`. This vulnerability affects runtime in-memory overrides only, which are non-persistent and cleared on restart. The `/debug` command is disabled by default and requires prior authorization to invoke, with no unauthenticated exploitation vector identified. The issue is addressed in the planned release 2026.2.21 by blocking reserved prototype keys during deep merges and sanitizing nested object values. This vulnerability is considered a defense-in-depth hardening measure rather than a critical security flaw.
OpenClaw CLI versions up to 2026.2.25 contain a vulnerability where the approval context for node system.run executions can be bypassed by rebinding a writable parent symlink in the current working directory (cwd) after approval. This allows a command approved for one filesystem location to execute from a different location if the parent symlink changes between approval and execution. The issue is fixed in version 2026.2.26 by enforcing immutable approval-time plan preparation and rejecting mutable parent-symlink path components during approval-plan building.