Safeguard
Vulnerability Analysis•

CVE-2026-27002: Critical Docker Sandbox Escape in OpenClaw

CVE-2026-27002 allows dangerous Docker options in the OpenClaw tool sandbox, enabling container escape. Upgrade to 2026.2.15 and review sandbox settings.

Safeguard Security Team
2 min read

CVE-2026-27002 is a critical (CVSS 9.8) configuration injection in the OpenClaw Docker tool sandbox before version 2026.2.15. Dangerous Docker options such as bind mounts, host networking and unconfined profiles could be applied, enabling container escape or host data access. Upgrade to 2026.2.15.

What's affected

OpenClaw, a personal AI assistant, in versions before 2026.2.15. The release adds blocks on dangerous sandbox Docker settings, runtime enforcement when building docker create arguments, config schema checks for network host, seccompProfile unconfined and apparmorProfile unconfined, and security audit findings for dangerous sandbox settings.

How to check if you're exposed

Check your OpenClaw version against 2026.2.15. Then review your configuration for the sandbox Docker keys the advisory names:

  • agents.*.sandbox.docker.binds that mount system directories or the Docker socket
  • agents.*.sandbox.docker.network set to anything other than none or bridge
  • unconfined values for the seccomp or AppArmor profiles

Any of these on an older version is the exposure the advisory describes.

What to do now

  1. Upgrade OpenClaw to 2026.2.15 or later.
  2. Remove bind mounts of system directories and Docker socket paths from sandbox settings.
  3. Keep the sandbox network at none, the default, or bridge.
  4. Do not use unconfined for seccomp or AppArmor profiles.
  5. Run the new security audit findings after upgrading and fix what they flag.

Why it matters

The record lists CWE-250, execution with unnecessary privileges. A sandbox exists to limit what code can touch. If a configuration can add host mounts, host networking or disabled profiles, the boundary no longer holds, and anything running inside can reach the host.

Tools that run model driven code need that boundary to hold by default. The fix enforces limits at runtime, not only in the config schema. The record does not mark this CVE as known exploited.

Quick check

What is the quickest mitigation if I cannot upgrade today?

The advisory says to avoid risky binds, keep the sandbox network at none or bridge and never use unconfined security profiles.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.