Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.
Open advisories
4 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.
Under iMessage groupPolicy=allowlist, group authorization could be satisfied by sender identities coming from the DM pairing store, broadening DM trust into group contexts. Details Affected component: src/imessage/monitor/monitor-provider.ts. Vulnerable logic derived effectiveGroupAllowFrom using both the static group allowlist and DM pairing-store identities (storeAllowFrom). This allowed a sender approved via DM pairing to satisfy group authorization in groups even if the sender/chat was not explicitly present in groupAllowFrom. This weakens boundary separation between DM pairing and group allowlist authorization. Affected Packages / Versions - openclaw (npm): affected <= 2026.2.13 - clawdbot (npm): affected <= 2026.1.24-3 Fix Commit(s) - openclaw/openclaw@872079d42fe105ece2900a1dd6ab321b92da2d59 - openclaw/openclaw@90d1e9cd71419168b2faa54a759b124a3eacfae7 Thanks @vincentkoc for reporting.
Recommended action: Upgrade to 2026.2.14 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Two related vulnerabilities existed in the macOS application's SSH remote connection handling (CommandResolver.swift): Details The sshNodeCommand function constructed a shell script without properly escaping the user-supplied project path in an error message. When the cd command failed, the unescaped path was interpolated directly into an echo statement, allowing arbitrary command execution on the remote SSH host. The parseSSHTarget function did not validate that SSH target strings could not begin with a dash. An attacker-supplied target like -oProxyCommand=... would be interpreted as an SSH configuration flag rather than a hostname, allowing arbitrary command execution on the local machine. Impact An attacker who can influence a user's remote connection settings (via social engineering or malicious configuration) could achieve arbitrary code execution on either the user's local machine or their configured remote SSH host, depending on which input vector is exploited. Affected…
Recommended action: Upgrade to 2026.1.29 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
The Control UI trusts gatewayUrl from the query string without validation and auto-connects on load, sending the stored gateway token in the WebSocket connect payload. Clicking a crafted link or visiting a malicious site can send the token to an attacker-controlled server. The attacker can then connect to the victim's local gateway, modify config (sandbox, tool policies), and invoke privileged actions, achieving 1-click RCE. This vulnerability is exploitable even on instances configured to listen on loopback only, since the victim's browser initiates the outbound connection. Details The root cause is the lack of validation for gatewayUrl combined with auto‑connect behavior on page load. With the change users now need to confirm the new gateway URL in the UI. Impact This is a token exfiltration vulnerability that leads to full gateway compromise. It impacts any Moltbot deployment where a user has authenticated to the Control UI. The attacker gains operator-level access to the…
Recommended action: Upgrade to 2026.1.29 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
A Command Injection vulnerability existed in Clawdbot’s Docker sandbox execution mechanism due to unsafe handling of the PATH environment variable when constructing shell commands. An authenticated user able to control environment variables could influence command execution within the container context. This issue has been fixed and regression tests have been added to prevent reintroduction. Impact In environments where Docker sandbox mode was enabled, authenticated users capable of supplying environment variables could affect the behavior of commands executed inside the container. This could lead to: 1. Execution of unintended commands inside the container 2. Access to the container filesystem and environment variables 3. Exposure of sensitive data 4. Increased risk in misconfigured or privileged container environments
Recommended action: Upgrade to 2026.1.29 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.