CVE-2026-32038
Sandbox Network Isolation Bypass in OpenClaw Enables Cross-Container Access
Publication date: 2026-03-19
Last updated on: 2026-03-23
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| openclaw | openclaw | to 2026.2.24 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-284 | The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. |
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know
Can you explain this vulnerability to me?
This vulnerability exists in OpenClaw versions before 2026.2.24 and involves a sandbox network isolation bypass. It allows trusted operators to join the network namespace of another container. By configuring the docker.network parameter with container:<id> values, attackers can access services inside target container namespaces, effectively bypassing network hardening controls.
How can this vulnerability impact me? :
The vulnerability can have a severe impact as it allows attackers to bypass network isolation between containers. This can lead to unauthorized access to services running inside other containers, potentially exposing sensitive data, compromising containerized applications, and undermining the security boundaries intended by container network isolation.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know