OpenClaw EUVD-2026-29146

Upgrade to OpenClaw version 2026.4.20 or later, which introduces comprehensive authorization guards blocking model-driven config.patch and config.apply mutations to operator-trusted configuration paths including sandbox policies, plugin enablement, gateway authentication/TLS settings, hook routing, MCP server configuration, SSRF policies, and filesystem hardening controls. The fix also prevents guard bypass via per-agent overrides and array-entry patching under agents.list[]. Installation via npm: 'npm install openclaw@2026.4.20' or 'npm update openclaw'. Vendor advisory and patch details available at https://github.com/openclaw/openclaw/security/advisories/GHSA-7jm2-g593-4qrc. If immediate patching is not feasible, implement these compensating controls with their trade-offs: (1) Disable or restrict the gateway tool from agent access by removing it from the agents.defaults.tools allowlist-this prevents legitimate model-driven gateway management workflows but eliminates the attack vector entirely. (2) Implement strict input validation and prompt injection detection on all user-supplied content reaching models with gateway tool access-reduces risk but cannot guarantee prevention of sophisticated injection techniques. (3) Enable comprehensive audit logging for all config.patch and config.apply operations with alerting on changes to protected paths listed in the advisory (sandbox, plugins.*, hooks.*, browser.ssrfPolicy, mcp.servers, tools.fs)-provides detection but not prevention, requiring manual incident response. (4) Run OpenClaw agents in isolated environments with read-only configuration mounted from external sources and restart-based configuration changes only-eliminates runtime mutation capability but sacrifices dynamic reconfiguration features. Each workaround involves operational friction and should be considered temporary until upgrade completion.