How severe is CVE-2026-27002?

No CVSS score has been assigned to CVE-2026-27002 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-27002?

CVE-2026-27002 affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix CVE-2026-27002?

Update openclaw to 2026.2.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-27002 is resolved across your whole dependency graph.

How do I detect CVE-2026-27002 in my npm dependencies?

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.

How do I mitigate CVE-2026-27002 if there is no patch (or I can't update yet)?

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.

Is CVE-2026-27002 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-27002 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-27002?

CVE-2026-27002 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 45th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-27002?

CVE-2026-27002 is classified as CWE-250 (CWE-250). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-27002 published, and has it been updated?

CVE-2026-27002 was published on February 19, 2026 and was last updated on November 4, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

CVE-2026-27002 — openclaw

Fix: openclaw/openclaw@887b209

CVE-2026-27002 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 asGHSA-w235-x559-36mg

Published

Feb 19, 2026

Updated

Nov 4, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 29, 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 CVE-2026-27002.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk-0.15%

Lower risk than most CVEs45th percentile — riskier than 45% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

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.

132other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

openclawnpm

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

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	all versions	2026.2.15`npm install openclaw@2026.2.15`

Affected Products

1 product · 1 configurations

Application

openclawopenclaw

< 2026.2.15

range

Detection & mitigation playbook

Open-source dependency

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.
Fix
Update openclaw to 2026.2.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-27002 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.

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 CVE-2026-27002 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works