Summary
OpenClaw: Docker container escape via unvalidated bind mount config injection
A configuration injection issue in the Docker tool sandbox could allow dangerous Docker options (bind mounts, host networking, unconfined profiles) to be applied, enabling container escape or host data access.
Affected Packages / Versions
- Package:
openclaw(npm) - Affected versions:
<= 2026.2.14 - Fixed version:
>= 2026.2.15(next release)
Workarounds
- Do not configure
agents.*.sandbox.docker.bindsto mount system directories or Docker socket paths. - Keep
agents.*.sandbox.docker.networkatnone(default) orbridge. - Do not use
unconfinedfor seccomp/AppArmor profiles.
Fix Commit(s)
- 887b209db47f1f9322fead241a1c0b043fd38339
- 1b6704ef5800152c777ea52b77aa2c8a46c13705 (docs)
Release Process Note
This advisory is pre-populated with the planned fixed version (>= 2026.2.15). Once [email protected] is published to npm, publishing this advisory should be a single-click action.
Thanks @aether-ai-agent for reporting.
Impact
If an attacker can influence sandbox Docker configuration (or an operator pastes untrusted config), they may be able to:
- mount sensitive host paths (e.g.
/etc,/proc,/sys,/dev, Docker socket) - use
network=hostto bypass container network isolation - use
seccompProfile=unconfined/apparmorProfile=unconfinedto weaken isolation
This can lead to host secret exfiltration or full host control (via Docker socket exposure).
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
OpenClaw now blocks dangerous sandbox Docker settings:
- runtime enforcement when building
docker createargs - config-schema validation for
network=host,seccompProfile=unconfined,apparmorProfile=unconfined - security audit findings to surface dangerous sandbox docker config
Frequently Asked Questions
- What is CVE-2026-27002? CVE-2026-27002 is a high-severity security vulnerability in openclaw (npm), affecting versions < 2026.2.15. It is fixed in 2026.2.15.
- Which versions of openclaw are affected by CVE-2026-27002? openclaw (npm) versions < 2026.2.15 is affected.
- Is there a fix for CVE-2026-27002? Yes. CVE-2026-27002 is fixed in 2026.2.15. Upgrade to this version or later.
- Is CVE-2026-27002 exploitable, and should I be worried? Whether CVE-2026-27002 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-27002 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-27002? Upgrade
openclawto 2026.2.15 or later.