CVE-2026-28457
Path Traversal in OpenClaw Sandbox Skill Mirroring Allows File Write
Publication date: 2026-03-05
Last updated on: 2026-03-09
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| openclaw | openclaw | to 2026.2.14 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-22 | The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in OpenClaw versions prior to 2026.2.14 and involves a path traversal issue in the sandbox skill mirroring feature. When this feature is enabled, it uses the skill frontmatter name parameter without proper sanitization while copying skills into the sandbox workspace. Attackers can exploit this by providing a specially crafted skill package with traversal sequences like "../" or absolute paths in the name field, allowing them to write files outside the intended sandbox workspace root directory.
How can this vulnerability impact me? :
The vulnerability allows attackers to write files outside the sandbox workspace, potentially leading to unauthorized file creation or modification on the system where OpenClaw is running. This can compromise the integrity of the system by overwriting or adding files in sensitive locations, which may lead to further exploitation or disruption of normal operations.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
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