Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain approval for benign script command
-
ExploitRewrite referenced script file on disk
-
ImpactExecute modified code under approved run context
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization logic validation
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires OpenClaw before version 2026.3.11 with script runners tsx or jiti enabled. Authenticated user with approval privileges must click malicious link or be socially engineered to approve a benign script command. Attacker then rewrites the referenced script file on disk before execution. |
| Impact | The CVSS 4.0 vector indicates network-accessible attack (AV:N) with low complexity (AC:L) requiring low privileges (PR:L) and user interaction (UI:P), resulting in critical 9.4 severity with high impact across all CIA dimensions. The authentication requirement (PR:L) and mandatory user interaction (UI:P) provide some natural barriers - attackers must hold valid low-privilege credentials and socially engineer approval from authorized users. However, the low attack complexity and network vector enable remote exploitation once these conditions are met. Without EPSS data or KEV listing for this future-dated CVE (2026), exploitation probability cannot be quantified through predictive modeling. The availability of detailed vendor advisories (GHSA-qc36-x95h-7j53 and VulnCheck write-up) provides attackers with implementation details, increasing weaponization risk. The TOCTOU nature makes this potentially automatable once initial access and approval are obtained. Real-world risk is HIGH for organizations using OpenClaw with tsx/jiti runners in production, particularly in environments where approval workflows are routinely granted or where attackers have established low-privilege foothold access. |
| Exploit ScenarioDerived | A remote attacker with low-privilege OpenClaw credentials crafts a benign JavaScript utility script and submits it for system.run approval through the organization's workflow. Once an administrator approves the seemingly harmless script execution via the UI, the attacker immediately overwrites the script file on disk with malicious payload code (reverse shell, credential stealer, or lateral movement tool) exploiting the window between approval grant and actual execution by the tsx or jiti runner. Because the approval system fails to bind the file's content or hash at authorization time, the execution engine runs the modified malicious script under the approved context, granting the attacker elevated execution privileges and potentially full system compromise depending on the run context's permissions. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Mar 29, 2026
Approval bypass in OpenClaw before 2026.3.11 allows low-privileged remote attackers to execute arbitrary code by exploiting race conditions in system.run approvals. Attackers obtain legitimate approval for benign scripts, then overwrite referenced files before execution via vulnerable tsx/jiti runners. With CVSS 9.4 (critical severity, network-accessible, low complexity) and EPSS data not yet available for this 2026 CVE, organizations using OpenClaw's script execution features face immediate risk despite requiring user interaction and low-level authentication. No public exploit identified at time of analysis, though the approval bypass mechanism is documented in vendor advisory GHSA-qc36-x95h-7j53.
RemediationAI
Upgrade immediately to OpenClaw version 2026.3.11 or later, which implements proper file operand binding for system.run approvals across all script runners including tsx and jiti. The patched version should cryptographically hash or lock file references at approval time to prevent TOCTOU exploitation. Until patching is possible, implement compensating controls including disabling tsx and jiti runners if not operationally required, enforcing strict file system permissions to prevent script modification by low-privileged users, implementing file integrity monitoring on script directories, and requiring elevated approval workflows with reduced approval validity windows to minimize TOCTOU opportunity. Review recent system.run approval logs for suspicious patterns of script modifications immediately following approvals. Consult the official security advisory at https://github.com/openclaw/openclaw/security/advisories/GHSA-qc36-x95h-7j53 for additional vendor-specific guidance and migration assistance.
Affected VersionsENISA
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 vulnerability affects OpenClaw (cpe:2.3:a:openclaw:openclaw), a command execution framework. The flaw stems from CWE-863 (Incorrect Authorization) in the system.run approval mechanism. When processing execution requests through certain JavaScript runtime interpreters (tsx and jiti), the approval system fails to implement proper time-of-check-time-of-use (TOCTOU) protections by not binding file operands at approval time. The approval validates the script content initially presented but does not lock or hash the file reference, allowing attackers to modify the script on disk between approval and execution. This breaks the fundamental security assumption that approved code matches executed code, effectively bypassing the authorization control meant to prevent arbitrary command execution.
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:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
Lifecycle Timeline
2DescriptionCVE.org
OpenClaw before 2026.3.11 contains an approval integrity vulnerability where system.run approvals fail to bind mutable file operands for certain script runners like tsx and jiti. Attackers can obtain approval for benign script commands, rewrite referenced scripts on disk, and execute modified code under the approved run context.
Blast Radius
ecosystem impact- 3 npm packages depend on openclaw (3 direct, 0 indirect)
Ecosystem-wide dependent count for version 2026.3.11.
Executive ViewAI
OpenClaw versions before 2026.3.11 contain a critical approval bypass vulnerability (CVSS 9.4) that allows low-privileged authenticated users to execute arbitrary code by exploiting race conditions in script approval workflows. Attackers can obtain legitimate approval for benign scripts, then swap the underlying files before execution, directly undermining code review controls and enabling unauthorized command execution across systems relying on OpenClaw for automation. Organizations using OpenClaw's script execution features should immediately identify affected deployments and implement compensating controls, as the vulnerability remains unpatched and poses severe operational and security risks.
No vendor-released patch identified at time of analysis. Interim mitigations: (1) Restrict system.run approval permissions to trusted administrators only, removing low-privileged user access; (2) Enforce file integrity monitoring on script directories to detect unauthorized modifications between approval and execution; (3) Require code review approvals to be granted immediately before execution (eliminate time windows for file substitution); (4) Isolate OpenClaw instances and script execution environments from sensitive production systems; (5) Enable comprehensive audit logging of all approval grants, file modifications, and script executions for forensic analysis.
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
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Related Vulnerabilities in OpenClaw Authorization and Access Control
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
EUVD-2026-17016
GHSA-qc36-x95h-7j53
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB