GHSA-w235-x559-36mg
OpenClaw: Docker container escape via unvalidated bind mount config injection
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.
openclawnpmDescription
Summary
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)
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).
Fix
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
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | openclaw | all versions | 2026.2.15 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update openclaw to 2026.2.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w235-x559-36mg is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-w235-x559-36mg is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-w235-x559-36mg. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-w235-x559-36mg in your dependencies?
O3 detects GHSA-w235-x559-36mg across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.