OpenClaw
CVE-2026-41364
HIGH
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain SSH credentials
-
DeliveryUpload crafted tar with malicious symlinks
-
ExploitTrigger tar extraction in sandbox
-
ExecutionSymlinks followed to target paths
-
PersistArbitrary files overwritten
-
ImpactAchieve code execution or DoS
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Symlink resolution safety
|
| Exploitation Conditions | Exploitation requires valid SSH authentication credentials to an OpenClaw instance (CVSS PR:L indicates low-privileged authenticated access is sufficient). The SSH sandbox tar upload feature must be enabled and accessible to the authenticated user - if this feature is disabled or restricted to administrators only, the vulnerability cannot be exploited. The OpenClaw process must have sufficient filesystem permissions to write to the symlink target locations for the attack to succeed - targeting system directories like /etc requires the service to run with elevated privileges. The vulnerability affects network-accessible deployments (AV:N) with default or permissive sandbox configurations that do not employ additional symlink protection mechanisms such as chroot jails, bind mounts with nosymfollow options, or secure extraction libraries that refuse to follow symlinks outside extraction boundaries. |
| Impact | The CVSS 4.0 score of 7.2 reflects HIGH integrity and availability impact with NETWORK attack vector, LOW complexity, and LOW privileges required. The vulnerability requires authenticated access (PR:L) but no user interaction (UI:N), making it straightforward to exploit once credentials are obtained. Scope is UNCHANGED, meaning the impact is confined to the vulnerable component itself. While no public exploit has been identified and the CVE is not listed in CISA KEV, the technical simplicity of symlink attacks (readily achievable with standard tar command-line tools) makes this easily reproducible. The primary risk is to organizations running OpenClaw with SSH sandbox features enabled and exposed to authenticated users who may be compromised or malicious insiders. Real-world priority is MEDIUM-HIGH for affected deployments: the attack is simple and the impact severe (arbitrary file write can lead to configuration tampering, code execution via overwriting scripts/binaries, or denial of service), but exploitation requires valid authentication and the specific SSH sandbox tar upload feature must be in use. Organizations not using this feature or restricting SSH access to highly trusted users face lower practical risk despite the high CVSS score. |
| Exploit ScenarioDerived | An attacker with valid SSH credentials to an OpenClaw instance crafts a malicious tar archive containing a symbolic link named 'config' pointing to '/etc/cron.d/backdoor' and a regular file that will be extracted following that symlink. Upon uploading this archive to the SSH sandbox, OpenClaw extracts the contents without validating the symlink target. The application follows the symlink and writes the attacker's malicious cron job file to /etc/cron.d/backdoor, establishing persistent code execution. Alternatively, the attacker could target application configuration files, SSH authorized_keys, or systemd service definitions to achieve similar privilege escalation or persistence goals. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Apr 28, 2026
Remote authenticated attackers can overwrite arbitrary files on OpenClaw servers by uploading malicious tar archives containing symbolic links to the SSH sandbox feature. The vulnerability allows escaping sandbox restrictions to modify critical system files, enabling potential remote code execution or denial of service. Affects OpenClaw versions before 2026.3.31. No public exploit identified at time of analysis, with EPSS data unavailable for this recent CVE.
RemediationAI
Upgrade to OpenClaw version 2026.3.31 or later, which contains a fix for the symlink following vulnerability as documented in GitHub commit 3d5af14984ac1976c747a8e11581d697bd0829dc available at https://github.com/openclaw/openclaw/commit/3d5af14984ac1976c747a8e11581d697bd0829dc. Organizations unable to immediately upgrade should implement compensating controls: disable the SSH sandbox tar upload feature entirely if not operationally required; restrict SSH access to the OpenClaw service to only highly trusted administrative accounts using IP allowlisting and strong authentication (certificate-based rather than password); implement file integrity monitoring on critical system paths to detect unauthorized modifications; and deploy the application in containerized or virtualized environments with read-only root filesystems where possible to limit the impact of arbitrary file writes. Note that disabling tar upload may break deployment workflows, and restrictive access controls must be balanced against operational needs for legitimate file transfers.
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in npm
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
This is a classic symlink following vulnerability (CWE-59) in OpenClaw's SSH sandbox tar archive handling mechanism. When processing uploaded tar archives, the application fails to properly validate or sanitize symbolic links before extraction. An attacker can craft a tar archive where a symlink points outside the intended sandbox directory (e.g., pointing to /etc/passwd or application configuration files). During extraction, the application follows the symlink and writes attacker-controlled content to the symlink target location rather than within the sandbox boundary. This class of vulnerability is common in archive extraction routines that don't use secure extraction libraries or fail to check for path traversal sequences and symbolic link targets. The SSH sandbox context suggests this feature is designed for remote file transfer or deployment operations, making it an attractive target for authenticated attackers seeking privilege escalation or persistence mechanisms.
Know when Openclaw gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N
Primary rating from Vendor (vulncheck) · only source for this CVE.
CVSS VectorVendor: vulncheck
DescriptionCVE.org
OpenClaw before 2026.3.31 contains a symlink following vulnerability in SSH sandbox tar upload that allows remote attackers to write arbitrary files. Attackers can exploit this by uploading tar archives containing symlinks to escape the sandbox and overwrite files on the remote host.
Blast Radius
ecosystem impact- 1 npm packages depend on openclaw (1 direct, 0 indirect)
Ecosystem-wide dependent count for version 2026.3.31.
Executive ViewAI
CVE-2026-41364 affects OpenClaw servers prior to version 2026.3.31, allowing authenticated users to bypass sandbox controls and overwrite arbitrary system files through malicious tar archives, potentially enabling unauthorized code execution or service disruption. Organizations running vulnerable OpenClaw deployments face elevated risk of lateral movement and system compromise by internal or compromised user accounts. Immediate inventory and access control review is critical given the absence of vendor patches.
No vendor-released patch identified at time of analysis. Interim mitigations: (1) Restrict SSH sandbox feature access to authorized personnel only; (2) Implement upload filtering to block tar archives unless business-critical; (3) Enable file integrity monitoring (e.g., AIDE, Tripwire) on /etc and other critical system directories; (4) Enforce principle of least privilege on OpenClaw service accounts; (5) Monitor and alert on unexpected file modifications in system directories.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Affected Products (CPE)CVE.org
Related Vulnerabilities in OpenClaw Multiple Security Flaws
View all 11Auth bypass in OpenClaw voice-call extension before 2026.2.1. EPSS 0.68%. PoC and patch available.
Privilege escalation in OpenClaw (pre-2026.3.28) allows unauthenticated remote attackers to gain administrative access b
OpenClaw versions 2026.2.22 through 2026.2.24 contain a privilege escalation vulnerability that allows authenticated att
An authorization mismatch vulnerability in OpenClaw versions prior to 2026.3.1 allows authenticated users with operator.
OpenClaw versions prior to 2026.1.29 automatically establish WebSocket connections to attacker-controlled gateway URLs e
Path traversal in OpenClaw through version 2026.3.23 enables unauthenticated remote attackers to read arbitrary files in
Authentication bypass in OpenClaw before 2026.5.3 allows remote attackers with low privileges to receive agent responses
Directory-context bypass in OpenClaw before 2026.8.1 allows authenticated attackers with user interaction to reuse an 'a
Unauthenticated access to the noVNC observer interface in OpenClaw's Docker sandbox browser allows anyone who can reach
OpenClaw versions before 2026.2.26 allow authenticated attackers to write arbitrary files outside the workspace director
OpenClaw versions prior to 2026.2.22 contain a shell environment variable injection vulnerability in the system.run func
OpenClaw versions prior to 2026.2.22 contain a resource exhaustion vulnerability where the application fails to consiste
NVD
CVE.org
EPSS
Vulnrichment
GitHub
Exploit-DB