CVE-2026-32038: OpenClaw - Sandbox Network Isolation Bypass via docker.network=container Parameter
OpenClaw before 2026.2.24 contains a sandbox network isolation bypass vulnerability that allows trusted operators to join another container's network namespace. Attackers can configure the docker.network parameter with container:<id> values to reach services in target container namespaces and bypass network hardening controls.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
OpenClawto a version that resolves this vulnerability.Fixed in 2026.2.24 - Configuration
Disallow or validate docker.network values of the form 'container:<id>' so operators cannot configure docker.network to join another container's network namespace.
OpenClaw docker.network = container:<id> - Compensating control
Restrict who can modify OpenClaw configuration (in particular the docker.network parameter). Implement RBAC/ACLs or similar controls so only a minimal set of administrators may set or change docker.network to prevent operator misuse.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-32038?
CVE-2026-32038 is considered a critical vulnerability due to its potential to allow unauthorized access between container networks.
How do I fix CVE-2026-32038?
To fix CVE-2026-32038, upgrade OpenClaw to version 2026.2.24 or later.
Who is affected by CVE-2026-32038?
CVE-2026-32038 affects all versions of OpenClaw prior to 2026.2.24.
What does CVE-2026-32038 allow attackers to do?
CVE-2026-32038 allows trusted operators to bypass sandbox network isolation and access other container's network namespaces.
When was CVE-2026-32038 discovered?
CVE-2026-32038 was identified in OpenClaw version before 2026.2.24.