CVE-2026-27002: OpenClaw: Docker container escape via unvalidated bind mount config injection
OpenClaw versions before 2026.2.15 have a configuration injection issue in the Docker tool sandbox that could let dangerous Docker options such as bind mounts, host networking and unconfined security profiles be applied. This could enable container escape or access to host data. Upgrading to 2026.2.15 and following the documented workaround reduces this risk.
Overview
OpenClaw is a personal AI assistant. According to the GitHub Security Advisory and the record description, a configuration injection issue in its Docker tool sandbox could allow dangerous Docker options to be applied. The record classifies the weakness as CWE-250 (Execution with Unnecessary Privileges).
Impact
- The description states that the issue could enable container escape or host data access.
- The NVD base score is 9.8 (critical), with high confidentiality, integrity and availability impact in the vector.
- The GitHub CNA assigned a lower score of 7.7, so the severity depends on the scoring source consulted.
Affected products and versions
- Product: Openclaw Openclaw.
- Affected: before 2026.2.15.
- The release 2026.2.15 is listed as the fixed version in the record.
Exploitation status
The record shows that this CVE is not listed in the CISA KEV catalog. No confirmed active exploitation appears in the sources consulted. The SSVC fields in the record indicate exploitation none and automatable no.
Remediation and mitigation
- Upgrade OpenClaw to 2026.2.15 or later.
- Until the upgrade is applied, do not configure sandbox bind mounts that expose system directories or container runtime socket paths.
- Keep the sandbox network mode at none (default) or bridge, and avoid host networking.
- Do not use unconfined seccomp or AppArmor profiles.
- Review the security audit findings that surface dangerous sandbox Docker settings.
Detection guidance
- Review OpenClaw configuration for sandbox Docker bind mounts, network mode and security profile settings.
- Use the security audit output included in the fixed release to identify dangerous sandbox settings.
- Monitor container hosts for unexpected containers that have host-path mounts or host networking.
Limitations of the available information
- The record does not describe specific exploitation steps, and it does not provide proof-of-concept details.
- The exact technical root cause in the code is not detailed in the record beyond the advisory references.
- No exploitation data beyond the KEV and SSVC fields is available in the record.
Frequently asked questions
Which OpenClaw versions are affected by CVE-2026-27002?
According to the record, versions before 2026.2.15 are affected. The record lists 2026.2.15 as the version that blocks the dangerous sandbox Docker settings.
Is this vulnerability known to be actively exploited?
The record shows that the CVE is not listed in the CISA KEV catalog, and no confirmed active exploitation appears in the sources consulted.
What should administrators do now?
Upgrade to 2026.2.15 or later. Until then, avoid bind mounts of system directories or runtime socket paths, keep the sandbox network at none or bridge, and do not use unconfined seccomp or AppArmor profiles.
This analysis was drafted with AI assistance from verified source data and automatically checked against it.