2026.10.7
8 months ago
1 days ago
Known vulnerabilities in the openclaw package. This does not include vulnerabilities belonging to this package’s dependencies.
Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.
Fix for free| Vulnerability | Vulnerable Version |
|---|---|
openclaw is a 🦞 OpenClaw — Personal AI Assistant Affected versions of this package are vulnerable to Incorrect Authorization via insufficient authorization checks in the How to fix Incorrect Authorization? Upgrade | <2026.7.1 |
openclaw is a 🦞 OpenClaw — Personal AI Assistant Affected versions of this package are vulnerable to Authorization Bypass Through User-Controlled Key via the How to fix Authorization Bypass Through User-Controlled Key? Upgrade | <2026.8.1 |
openclaw is a 🦞 OpenClaw — Personal AI Assistant Affected versions of this package are vulnerable to Incorrect Authorization via glob metacharacter interpretation and node display name reuse in file-transfer Note: Exploitation requires a prior operator How to fix Incorrect Authorization? Upgrade | <2026.8.1 |
openclaw is a 🦞 OpenClaw — Personal AI Assistant Affected versions of this package are vulnerable to Insertion of Sensitive Information into Log File via the OpenAI-compatible transport layer, when a pinned third-party provider session whose resolved model metadata lacks a concrete base URL continues after a model configuration hot reload. Under this condition, the session retains the third-party provider's credential while the OpenAI SDK falls back to its own default endpoint, causing a request to be sent to an unrelated provider endpoint carrying that credential. The disclosure results in a failed request with a misleading authentication error, and the exposed credential should be rotated. Note: This is only exploitable when a third-party provider uses an OpenAI-compatible API, the resolved model metadata lacks an explicit provider base URL, and an existing pinned session continues after model configuration is reloaded. How to fix Insertion of Sensitive Information into Log File? Upgrade | <2026.8.1 |
openclaw is a 🦞 OpenClaw — Personal AI Assistant Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling via the Browser extension relay, which reserves entries in a single global pending-authentication pool before a client proves possession of the relay key. An unauthenticated network source can hold every pending slot by maintaining silent WebSocket upgrades, preventing paired extensions from completing Browser Relay Authentication v2. The issue does not disclose the relay key, browser data, or authenticated relay capability. How to fix Allocation of Resources Without Limits or Throttling? Upgrade | <2026.8.2 |
openclaw is a 🦞 OpenClaw — Personal AI Assistant Affected versions of this package are vulnerable to Insertion of Sensitive Information into Log File in the How to fix Insertion of Sensitive Information into Log File? Upgrade | <2026.9.1 |
openclaw is a 🦞 OpenClaw — Personal AI Assistant Affected versions of this package are vulnerable to Incorrect Behavior Order: Validate Before Canonicalize via incorrect classification of alternate Note: This is only exploitable when an operator connects How to fix Incorrect Behavior Order: Validate Before Canonicalize? Upgrade | <2026.8.1 |
openclaw is a 🦞 OpenClaw — Personal AI Assistant Affected versions of this package are vulnerable to Insertion of Sensitive Information into Log File via the memory embedding failover logic, where the primary embedding provider's configured API key is reused when a request is redirected to a fallback provider. When remote embedding fallback is configured and the primary provider fails, the credential is transmitted as a bearer token to an unintended vendor. The practical impact depends on the configured providers, whether failover occurs, and the privileges attached to the primary provider key. Note: This is only exploitable when remote embedding fallback is configured and the primary embedding provider fails, causing a cross-provider failover. How to fix Insertion of Sensitive Information into Log File? Upgrade | >=2026.3.28 <2026.8.1 |
openclaw is a 🦞 OpenClaw — Personal AI Assistant Affected versions of this package are vulnerable to Directory Traversal via double-decoding of QQBot voice attachment filenames, where encoded traversal segments reappear after sanitization. An attacker who can supply a voice attachment through a remote QQ sender can cause the agent to write attacker-controlled bytes outside the intended voice staging directory to any other process-writable location. How to fix Directory Traversal? Upgrade | <2026.8.1 |
openclaw is a 🦞 OpenClaw — Personal AI Assistant Affected versions of this package are vulnerable to Missing Authorization via the How to fix Missing Authorization? Upgrade | <2026.7.1 |
openclaw is a 🦞 OpenClaw — Personal AI Assistant Affected versions of this package are vulnerable to Incorrect Authorization via reusable exec approvals that fail to bind the working directory context to the approval record. When an operator grants an How to fix Incorrect Authorization? Upgrade | <2026.8.1 |
openclaw is a 🦞 OpenClaw — Personal AI Assistant Affected versions of this package are vulnerable to Arbitrary Code Injection via the upstream API requests. An attacker can execute arbitrary code by injecting malicious prompts into requests. How to fix Arbitrary Code Injection? There is no fixed version for | >=0.0.0 |