OpenClaw versions prior to 2026.2.24 contain a sandbox bind validation vulnerability allowing attackers to bypass allowed-root and blocked-path checks via symlinked parent directories with non-existent leaf paths. Attackers can craft bind source paths that appear within allowed roots but resolve outside sandbox boundaries once missing leaf components are created, weakening bind-source isolation enforcement.
Security readout for executives and security teams
Plain-English summary
OpenClaw before 2026.2.24 can be tricked into accepting sandbox bind paths that later point outside intended boundaries. This can weaken isolation for local users who can supply bind paths, with a stronger integrity impact than confidentiality impact.
Executive priority
Treat as a moderate-priority platform isolation issue. Prioritize systems where OpenClaw handles untrusted local workloads or user-controlled sandbox paths, because the main business risk is unauthorized file integrity impact outside expected boundaries.
Technical view
The flaw is a sandbox bind validation bypass. A symlinked parent with a missing final path component can pass allowed-root and blocked-path checks, then resolve outside the sandbox once the missing component exists. Sources classify it as CWE-22 with CVSS 4.0 score 6.9.
Likely exposure
Exposure is most likely where OpenClaw is used with sandbox bind mounts and low-privileged or untrusted local users can influence bind source paths. The source bundle does not indicate remote network exposure.
Exploitation context
The CVSS vector indicates local access, low complexity, low privileges, and no user interaction. KEV is false, and the provided sources do not state active exploitation.
Researcher notes
Evidence supports a path traversal-style validation bypass in bind-source handling. Public sources name a patch and affected versions before 2026.2.24. No exploit code, active exploitation, or broader affected products are established in the provided bundle.
Mitigation direction
Upgrade OpenClaw to 2026.2.24 or later.
Review the GitHub advisory and patch commit for vendor guidance.
Restrict who can define sandbox bind source paths.
Reduce or remove symlinked bind sources where operationally feasible.
Validation and detection
Inventory OpenClaw deployments and record installed versions.
Identify workflows where users can supply bind source paths.
Confirm patched builds include commit b5787e4abba0dcc6baf09051099f6773c1679ec1 or later.
Review sandbox configuration for symlink-dependent bind paths.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-22 · source CWE mapping
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.