CVE
CVE-2026-44113
Openclaw · Openclaw
- First Reported
- May 15, 2026
- Latest Reported
- May 18, 2026
CVE Enrichment
- CVSS
- 8.3 HIGH
- EPSS
- 0.25%
- EPSS Percentile
- 16.28%
- CISA KEV
- Not listed
Description
OpenClaw before 2026.4.22 contains a time-of-check/time-of-use race condition in the OpenShell filesystem bridge that allows attackers to read files outside the intended mount root. Attackers can exploit symlink swaps during filesystem operations to bypass sandbox restrictions and access unauthorized file contents.
Technical Details
- CVSS Version
- 4.0
- CNA / NVD Source
- [email protected]
- Published
- 07-May-2026 03:16
- Last Modified
- 17-Jun-2026 17:50
- EPSS Date
- 2026-11-02
- CWE
- CWE-367
CVSS Vector
CVSS:4.0 AV:N /
AC:L /
AT:N /
PR:L /
UI:N /
VC:H /
VI:N /
VA:N /
SC:H /
SI:N /
SA:N /
E:X /
CR:X /
IR:X /
AR:X /
MAV:X /
MAC:X /
MAT:X /
MPR:X /
MUI:X /
MVC:X /
MVI:X /
MVA:X /
MSC:X /
MSI:X /
MSA:X /
S:X /
AU:X /
R:X /
V:X /
RE:X /
U:X
Affected Products / Versions
- openclaw / openclaw
Source: NVD CPE · affected
Version / affected range: * · before (exclusive) 2026.4.22
cpe:2.3:a:openclaw:openclaw:*:*:*:*:*:node.js:*:*
References
Last enrichment sync: 03-Nov-2026 11:58
Sources: NVD · FIRST EPSS · CISA KEV
Latest successful provider update; providers refresh independently.
Sources: NVD · FIRST EPSS · CISA KEV
Latest successful provider update; providers refresh independently.
Reported Context (2)
- After gaining code execution within the OpenShell sandbox, the attacker can exploit a race condition (CVE-2026-44113) to read files outside the mount root, or an exec allowlist analysis bug (CVE-2026-44115) to execute Cyera Details Four OpenClaw Flaws That Can Enable Sandbox Escape and Backdoors
- #ClawChain Four OpenClaw Flaws Could Enable Data Theft, Privilege Escalation and Persistence
CVE (3)
People (1)
MITRE ATT&CK (3)
Products (2)
Note: Related entities, including threat actors, malware, CVEs, MITRE ATT&CK techniques, vendors, products, tools, countries, and industries, are shown when they appear in the same reporting. Their presence does not necessarily mean they were targeted, compromised, vulnerable, responsible for the activity, or directly involved in the incident.
