Critical OpenClaw Security Vulnerabilities Patched in 2026.3.28

Critical Security Issues in OpenClaw Core
Ant AI Security Lab identified 33 vulnerabilities in OpenClaw's framework, with 8 critical issues patched in the 2026.3.28 release. These vulnerabilities expose fundamental trust boundary problems in how agents are deployed.
Specific Vulnerabilities and Their Impact
Sandbox Isolation Bypass
In versions ≤2026.3.24, the message tool accepts mediaUrl and fileUrl aliases that bypass sandbox validation. This allows agents constrained to a sandbox to read arbitrary local files through these alias parameters, rendering isolation ineffective.
Privilege Escalation via Device Pairing
The /pair approve command path was calling device approval without forwarding caller scopes into the core check. This means users with basic pairing privileges could approve pending device requests asking for broader scopes, including full admin access, effectively granting themselves permissions they don't have.
Token Revocation Ineffectiveness
When tokens are revoked for suspected compromised devices, the gateway only updates stored credentials without disconnecting already-authenticated WebSocket sessions. Revoked devices can continue using live sessions until connections naturally drop.
SSRF Vulnerability in Image Provider
When using the fal provider for image generation, it uses raw fetches for both API traffic and image downloads, skipping the SSRF-guarded fetch path. This allows malicious relays to force the gateway to fetch internal URLs and expose internal service responses through the image pipeline.
Allowlist Degradation
Route-level group allowlists for platforms like Google Chat or Zalo were silently downgrading from allowlist to open instead of preserving group policies. This allows any member of the allowlisted space to interact with the bot, ignoring sender-level restrictions.
Immediate Actions Required
- Check your OpenClaw version. If it's ≤2026.3.24, update to 2026.3.28 immediately.
- Review pairing logs for any unexpected admin grants.
- If you recently revoked a token, force-restart your gateway to kill lingering WebSocket sessions.
The Ant AI Security Lab audit reveals that while much attention focuses on LLM security risks like prompt injection, the framework's own parameter validation and trust boundaries present critical vulnerabilities. All 8 advisories from the audit are publicly available on the OpenClaw GitHub security tab.
📖 Read the full source: r/openclaw
👀 See Also

Zero-Trust OpenClaw Architecture Adds Pre-Execution Authorization and Post-Execution Verification
An open-source architecture for OpenClaw adds two security checkpoints: a Rust sidecar that intercepts tool calls before execution with sub-millisecond authorization overhead, and deterministic post-execution verification using assertions instead of LLM judgment. The system includes tracing with DOM snapshots and screenshots, plus a DOM compression skill that reduces token usage by 90-99%.

OpenClaw Security: The Hardened Baseline You Should Start With
Self-hosting OpenClaw doesn't automatically make it secure. A Reddit post details the hardened baseline config: local-only Gateway, per-peer DM isolation, deny runtime/fs/automation tool groups, exec locked down, and mention-gated groups.

Strict Read-Only Rules in Skill Files Are Instructions, Not Enforcement
A Reddit user reports an OpenClaw agent with a strict 'READ-ONLY — never post' rule was tricked into posting via prompt injection, highlighting that skill file rules are just instructions, not enforced constraints.

Claude implements identity verification for certain use cases
Anthropic is rolling out identity verification for Claude through Persona Identities, requiring government-issued photo IDs and live selfies. The verification process takes under five minutes and is used to prevent abuse and comply with legal obligations.