Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm
Not in CISA KEV

GHSA-w235-x559-36mg — openclaw

Fix: openclaw/openclaw@887b209

GHSA-w235-x559-36mg is a CWE-250 vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.

OpenClaw: Docker container escape via unvalidated bind mount config injection

Also known asCVE-2026-27002
Published
Feb 18, 2026
Updated
Feb 20, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Sep 22, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • A successful exploit gives an attacker total control of the affected component, not partial access.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-w235-x559-36mg.

EPSS Exploitation Probability

via FIRST.org ↗
0.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs41th percentile — riskier than 41% of all scored CVEsHighest risk

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.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

133other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
openclawnpm
2.5Mdownloads / week

Description

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=host to bypass container network isolation
  • use seccompProfile=unconfined / apparmorProfile=unconfined to 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 create args
  • 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.binds to mount system directories or Docker socket paths.
  • Keep agents.*.sandbox.docker.network at none (default) or bridge.
  • Do not use unconfined for 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

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmopenclawall versions2026.2.15npm install openclaw@2026.2.15

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. 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.

  3. 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.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-w235-x559-36mg can be triaged on real exposure rather than presence alone.

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

## 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=host`
O3 Security · Impact-Aware SCA

Is GHSA-w235-x559-36mg in your dependencies?

O3 Security finds GHSA-w235-x559-36mg across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works
GHSA-w235-x559-36mg: openclaw | O3 Security