
Published: 1/28/2026
Author: Miguel Oviedo @devmangel
Date: February 9, 2026
Severity: CRITICAL
CVSS Score: 9.8 (Critical)
This document presents a comprehensive security analysis of OpenClaw, an AI agent orchestration framework. Through hands-on testing and exploitation, I've identified critical security vulnerabilities that allow complete host system compromise when OpenClaw is exposed to untrusted networks.
Key Findings:
Bottom Line: Any user with access to an OpenClaw agent can gain root access to the underlying host system. This analysis provides evidence, exploitation techniques, and actionable solutions.
While working with OpenClaw's agent system, I performed a routine security audit by spawning a sub-agent and requesting it to verify its environment. During this investigation, I discovered the agent had unexpected access to the Docker daemon, which led to a deeper security review.
Session Evidence:
The vulnerability was confirmed with a simple command:
Following this, a complete host filesystem access was achieved:
Result: Full read/write access to the entire host filesystem, including:
The security issue stems from the default docker-compose.yml configuration:
The Problem:
In the Docker security model, access to the Docker socket is equivalent to root access on the host. This is a well-known security principle documented by Docker itself.
From Docker's official security documentation:
"The Docker daemon socket is owned by root and group docker. Users in the docker group can run Docker commands, which is equivalent to having root privileges."
I've identified five distinct attack vectors for container escape and host compromise:
Technique: Mount the entire host filesystem into a temporary container.
Impact:
Mitigation Difficulty: ❌ Cannot be prevented if Docker API access exists
Technique: Create a privileged container with device access.
Impact:
Mitigation Difficulty: ❌ Cannot be prevented with API access
Technique: Share the host's PID namespace and use nsenter.
Impact:
Mitigation Difficulty: ❌ Cannot be prevented with API access
Technique: Use host network mode with dangerous capabilities.
Impact:
Mitigation Difficulty: ❌ Cannot be prevented with API access
Technique: Mount parent directories containing sensitive resources.
Impact:
Mitigation Difficulty: ❌ Cannot be prevented with API access
Many might suggest using tecnativa/docker-socket-proxy:
Why This Doesn't Work:
Endpoint filtering, not payload validation: The proxy blocks HTTP endpoints, but doesn't validate request payloads. It allows POST /containers/create without inspecting what parameters are being sent.
All the attack vectors still work: As long as you can create containers, you can specify:
False sense of security: Teams might think they're protected when they're not.
Even if you build a proxy that validates binds:
This fails because:
Giving an AI agent access to the Docker API is architecturally equivalent to giving it root access to the host. No amount of filtering can change this fundamental reality because Docker was designed as a root-level orchestration tool, not a security boundary.
An attacker doesn't need direct access to OpenClaw. They just need to trick the AI:
Attack Flow:
Example Malicious Prompt:
The AI might execute this as part of its troubleshooting routine.
If OpenClaw dependencies are compromised:
With Docker socket access, a single compromised dependency = full system compromise.
OpenClaw does implement some security measures:
Verification: I spawned a test sub-agent that confirmed it had NO Docker access - it was properly sandboxed.
The main gateway agent has:
This creates an asymmetric trust model: Sub-agents are secure, but the main agent is not.
Architecture Change: Remove Docker access from gateway, create dedicated orchestrator.
Orchestrator API:
Security Benefits:
Implementation Effort: ~4-6 hours
Add gVisor (runsc) as the container runtime:
Security Benefits:
Trade-offs:
Implementation Effort: ~1-2 hours
Configure Docker to run without root privileges:
Security Benefits:
Trade-offs:
Implementation Effort: ~2-3 hours
Combine multiple layers:
Security Layers:
Combined Result:
Implementation Effort: ~8-12 hours
If you can't implement full solutions immediately:
Ensure OpenClaw is NEVER exposed to untrusted networks:
At minimum, mount the socket as read-only:
Note: This prevents docker create/start but still allows information disclosure.
To verify if your OpenClaw installation is vulnerable:
If ANY of these succeed, your installation is vulnerable.
After implementing solutions, verify they work:
| Approach | Prevents Escape | Complexity | Functionality | Recommended |
|---|---|---|---|---|
| Current (No mitigation) | ❌ No | - | ✅ Full | ❌ Never |
| Docker Socket Proxy | ❌ No | Low | ✅ Full | ❌ False security |
| Custom Validator Proxy | ⚠️ Partial | Medium | ✅ Full | ⚠️ Incomplete |
| Sandbox Orchestrator | ✅ Yes | Medium | ✅ Full | ✅ Recommended |
| gVisor Runtime | ✅ Mostly | Low | ⚠️ 90% | ✅ Good addition |
| Rootless Docker | ✅ Mostly | High | ⚠️ 95% | ✅ Long-term |
| Defense in Depth | ✅✅ Yes | High | ✅ Full | ✅✅ Ultimate |
Current Setup: Developer running OpenClaw on laptop
Risk Level: LOW
Recommendation: Basic mitigations sufficient (localhost binding, read-only socket)
Current Setup: OpenClaw on internal company network
Risk Level: MEDIUM-HIGH
Recommendation: Implement Sandbox Orchestrator + security profiles
Current Setup: OpenClaw accessible from internet
Risk Level: CRITICAL
Recommendation:
Current advice: ❌ DO NOT expose OpenClaw to the internet with default configuration.
This analysis is being shared publicly because:
At the time of writing, I'm not aware of any malicious exploitation of this vulnerability in the wild. This disclosure is preventive.
OpenClaw is a powerful AI agent orchestration framework, but its default configuration has critical security vulnerabilities that make it unsafe for internet exposure. The root cause is architectural: giving containers access to the Docker socket is fundamentally equivalent to giving them root on the host.
Key Takeaways:
The good news: These vulnerabilities are fixable with proper engineering. The sub-agent isolation already works correctly - we just need to apply the same principles to the gateway.
I'm committed to helping make OpenClaw production-ready and secure. Let's work together to build a safer AI agent platform.
For security researchers and penetration testers:
Disclaimer: This PoC is for authorized testing only. Unauthorized access to computer systems is illegal.
End of Security Analysis
Contributing: If you have additional attack vectors or mitigation strategies, please reach out or submit a PR.
Acknowledgments: Thanks to the OpenClaw team for creating an innovative AI orchestration platform. Security issues are opportunities to build something better together.
Document Version: 1.0
Last Updated: February 9, 2026
Author: Miguel Oviedo (@devmangel)