A security vulnerability in Craft CMS allows unauthenticated remote attackers to trigger activation emails for pending user accounts. This flaw stems from an improper access control configuration in the `UsersController`, permitting anonymous access to the `actionSendActivationEmail` endpoint. Exploitation facilitates user enumeration and potential phishing campaigns by allowing attackers to verify the existence of user IDs and spam registered email addresses.
A Missing Authorization vulnerability in Canonical LXD allows authenticated, restricted users to enumerate the fingerprints of all trusted certificates via the API. The flaw exists in the non-recursive handling of the GET /1.0/certificates endpoint, bypassing per-object visibility controls.
A critical access control vulnerability exists in the OpenClaw BlueBubbles plugin due to a logic error in the shared authorization utility. The flaw causes the system to fail-open when the allowlist configuration is empty, permitting unauthorized remote users to bypass Direct Message (DM) gating policies. This allows arbitrary unauthenticated users to interact with the AI assistant, potentially triggering sensitive actions or accessing private data.
OpenClaw (formerly Clawdbot) contains a critical authorization bypass vulnerability in its elevated permissions module. The vulnerability arises from an overly permissive validation logic in the `isApprovedElevatedSender` function, which incorrectly includes the message recipient's identifier (the bot itself) in the authorization check. If an administrator includes the bot's own identity in the `tools.elevated.allowFrom` configuration—a common configuration pattern for self-testing—any unauthenticated remote user can execute commands with elevated privileges by simply sending a message to the bot.
OpenClaw, a popular open-source AI assistant, was found to execute critical containerized processes with full root privileges. This configuration violates the principle of least privilege and significantly lowers the barrier for attackers to achieve persistence or container escape following a compromise. The vulnerability affects multiple Dockerfiles used for end-to-end testing and sandboxing.
A logical vulnerability exists in the authorization middleware of the OpenClaw BlueBubbles extension, enabling unauthorized users to bypass group chat access controls. The flaw allows the trusted identity of a user established in a Direct Message (DM) context—stored in a local pairing store—to incorrectly satisfy authorization requirements in Group Chat contexts, even when strict allowlists are configured. This effectively renders the `groupPolicy` allowlist ineffective against any user who has previously paired with the assistant via a private channel.
A critical remote code execution vulnerability exists in the OpenClaw automation platform (versions prior to 2026.2.23). The flaw resides in the 'safe-bin' allowlist validation logic, which fails to account for GNU long-option abbreviations when sanitizing command-line arguments. Low-privileged authenticated users can exploit this by supplying abbreviated flags (e.g., '--compress-p' instead of '--compress-program') to the 'sort' utility. This bypasses the security filter while still being interpreted by the underlying binary as a dangerous directive, allowing the execution of arbitrary system commands.
A critical path traversal vulnerability exists in the OpenClaw infrastructure, specifically within the webhook transform module loader. The vulnerability arises from improper resolution of symbolic links when validating module paths against a restricted directory allowlist. By creating a symbolic link within the allowed directory that points to a file outside of it, an attacker can bypass the containment check and force the application to load and execute arbitrary JavaScript or TypeScript files from the filesystem. This flaw allows for Remote Code Execution (RCE) if an attacker can introduce a symbolic link into the configured transforms directory.
A critical vulnerability in OpenClaw allows for the recovery of high-privilege gateway authentication tokens due to an insecure fallback mechanism in the privacy-preservation logic. When anonymizing owner identifiers for external LLM prompts, the system defaults to using the sensitive `gateway.auth.token` as a cryptographic salt if no dedicated display secret is configured. This results in the transmission of hashes derived from the authentication token to third-party providers, enabling offline brute-force attacks to recover the administrative credentials.
A critical authorization bypass vulnerability exists in the Synology Chat extension of the OpenClaw AI assistant infrastructure. The vulnerability arises from a 'fail-open' logic error in the user allowlist enforcement mechanism. When the `dmPolicy` is configured to `allowlist` but the list of allowed user IDs is left empty, the system defaults to permitting all traffic rather than denying it. This flaw allows unauthenticated remote attackers to interact with the AI agent, potentially triggering sensitive tools or workflows intended only for authorized administrators.
A critical Remote Code Execution (RCE) vulnerability exists in OpenClaw's `safeBins` execution allowlist mechanism. The flaw resides in the `tools.exec.safeBins` configuration logic, where a permissive generic fallback profile was applied to binaries lacking specific security definitions. This oversight allows attackers to bypass command approval policies by leveraging interpreter binaries (e.g., Python, Node.js) to execute arbitrary inline payloads, effectively neutralizing the intended security controls of the agent framework.
A capture-replay vulnerability exists in the Nextcloud Talk integration of the OpenClaw AI platform. The webhook handler properly verifies cryptographic signatures but fails to track processed message identifiers, allowing attackers to re-submit captured valid requests. This results in duplicate processing of AI commands and potential redundant side effects.
Or generate a custom report
Search for a CVE ID (e.g. CVE-2024-1234) to generate an AI-powered vulnerability analysis
Automated vulnerability intelligence. 959+ reports.