Container service access via network namespace join
Published Mar 19, 2026 · Updated Mar 19, 2026
Sandbox isolation bypass in OpenClaw before 2026.2.24 allows trusted operators to reach services in another container namespace. validateNetworkMode rejects only host mode, while buildSandboxCreateArgs forwards container: unchanged to Docker's --network argument. Reachability requires control of trusted sandbox network configuration; target services then become accessible from the sandbox despite network isolation.
Summary
What happened
Sandbox isolation bypass in OpenClaw before 2026.2.24 allows trusted operators to reach services in another container namespace. validateNetworkMode rejects only host mode, while buildSandboxCreateArgs forwards container: unchanged to Docker's --network argument. Reachability requires control of trusted sandbox network configuration; target services then become accessible from the sandbox despite network isolation.
The record
- CVE
- CVE-2026-32038
- Published
- Mar 19, 2026
- Updated
- Mar 19, 2026
- Vendor
- OpenClaw Foundation
- Product
- OpenClaw
- Classifications
- CWE-284, CWE-693
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 19, 2026CVE publishedPublication date reported by the CVE source.
- Mar 19, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2026.2.24
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo