OpenClaw's 'Allow Always' Feature Security Flaws and Safer Alternatives
OpenClaw Approval System Vulnerabilities
OpenClaw's approval system asks users "can I do this?" before running commands, with options to approve once or approve always. The "allow always" feature has been identified as a security risk through two recent CVEs.
Specific Security Issues
CVE-2026-29607: The "allow always" approval binds to the wrapper command, not the inner command. If you approve time npm test with "always," the system remembers "always allow time." Later, if the agent (or through prompt injection) runs time rm -rf /, it executes without re-prompting because you approved the wrapper command.
CVE-2026-28460: This vulnerability bypasses the allowlist entirely using shell line-continuation characters. Different technique but same outcome: commands execute without the approval check you thought was protecting you.
Both vulnerabilities are patched in OpenClaw 3.12+, but the deeper issue remains.
The Behavioral Security Problem
Even after patching, the "allow always" mental model trains users to stop paying attention. Initially, users carefully read every approval prompt. By week 3, they're clicking "always" on everything because prompts become annoying and trust builds in the agent. By week 6, users accumulate 20+ "always" rules they couldn't list if asked.
Recommended Alternative Approach
The source author recommends: no "allow always" for anything that modifies files, sends messages, or runs shell commands. Instead, add explicit guardrails in your SOUL.md file:
"for any action that modifies files, sends communications, or executes shell commands: show me exactly what you plan to do and wait for my explicit ok. previous approvals do not carry forward. ask every time. this is non-negotiable."
This approach means more tapping "ok" on interfaces like Telegram, but prevents the agent from being tricked via prompt injection or its own hallucination into executing destructive actions under stale approvals.
Key Takeaway
The approval system is a convenience feature that was never designed as a security boundary. Treat it accordingly.
📖 Read the full source: r/openclaw
👀 See Also
Agent Passport: Identity Verification for AI Agents
Agent Passport is an open-source identity verification layer using Ed25519 authentication and JWT tokens for AI agents, addressing the problem of agent impersonation.
ClawCare: Security Guard for AI Coding Agents After AWS Key Leak
ClawCare is a Python tool that scans commands before execution in AI coding agents like Claude Code, blocking risky patterns like bulk environment dumps and reverse shells. It was built after a developer accidentally leaked an AWS key through an agent.
OpenObscure: Open-Source On-Device Privacy Firewall for AI Agents
OpenObscure is an open-source, on-device privacy firewall that sits between AI agents and LLM providers. It uses FF1 Format-Preserving Encryption with AES-256 to encrypt PII values before requests leave your device, maintaining data structure while protecting privacy.
Open-Source Attack Surface Management Cheat Sheet Released
A developer has open-sourced an Attack Surface Management cheat sheet that covers practical workflows, tools, and references. The project includes sections on asset discovery, infrastructure tracking, reconnaissance tooling, automation workflows, and learning resources.