OpenClaw 2026.2.12 Released to Patch Over 40 Security Vulnerabilities
The OpenClaw team has released version 2026.2.12, introducing significant updates focused on security enhancements and architectural stability. This update addresses over 40 security vulnerabilities and stability issues within the AI agent framework.
The OpenClaw team has released version 2026.2.12, introducing significant updates focused on security enhancements and architectural stability. This update addresses over 40 security vulnerabilities and stability issues within the AI agent framework.
Enhancements to the gateway, sandbox isolation, and integration providers such as WhatsApp, Discord, and Slack. Addressing Server-Side Request Forgery (SSRF) risks by implementing explicit deny policies and hostname allowlists for input_file and input_image parameters. Introduction of a strict per-request URL input cap to mitigate potential denial-of-service vectors. Removal of the soul-evil hook component to eliminate potential malicious elements.
Gateway: Hardened URL handling with explicit deny policy and hostname allowlists. Hooks: Removal of malicious code. API: Fix for unauthenticated Nostr profile API remote config tampering. Sandbox: Confined skill sync destinations to prevent filesystem escapes. Web Tools: Stripped toolResult.details to reduce replay attack surface. BlueBubbles: Fixed webhook authentication bypass.
These upgrades prevent unauthorized access to internal network resources and enhance the security of agent operations.
The OpenClaw team has released version 2026.2.12, introducing significant updates focused on security enhancements and architectural stability.
WhatsApp: Ensures correct handling of voice messages with MIME type defaults. Slack: Improved command detection capabilities. Signal: Enforced E.164 validation for improved input accuracy.
The update introduces a necessary breaking change to the POST /hooks/agent endpoint, with the system now rejecting payload sessionKey overrides by default to prevent session hijacking. Administrators requiring legacy behavior must configure hooks.allowRequestSessionKey: true .
Authentication for browser control has been strengthened, requiring credentials for loopback browser control routes and auto-generating an auth token if one is missing during startup, thus preventing local attackers from hijacking the browser control interface.
For detailed information on the release, visit the official release page .
Based on reporting by GBHackers.
