CVE-2026-41355 | OpenClaw up to 2026.3.27 inclusion of functionality from untrusted control sphere (GHSA-42mx-vp8m-j7qh)

VDB-359309 · CVE-2026-41355 · GHSA-42MX-VP8M-J7QH OPENCLAW UP TO 2026.3.27 INCLUSION OF FUNCTIONALITY FROM UNTRUSTED CONTROL SPHERE HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 6.2 $0-$5k 1.96 Summaryinfo A vulnerability classified as problematic has been found in OpenClaw up to 2026.3.27. Impacted is an unknown function. The manipulation leads to inclusion of functionality from untrusted control sphere. This vulnerability is traded as CVE-2026-41355. An attack has to be approached locally. There is no exploit available. It is recommended to upgrade the affected component. Detailsinfo A vulnerability, which was classified as problematic, has been found in OpenClaw up to 2026.3.27. This issue affects some unknown processing. The manipulation with an unknown input leads to a inclusion of functionality from untrusted control sphere vulnerability. Using CWE to declare the problem leads to CWE-829. The product imports, requires, or includes executable functionality (such as a library) from a source that is outside of the intended control sphere. Impacted is confidentiality, integrity, and availability. The summary by CVE is: OpenShell before 2026.3.28 contains an arbitrary code execution vulnerability in mirror mode that converts untrusted sandbox files into workspace hooks. Attackers with mirror mode access can execute arbitrary code on the host during gateway startup by exploiting enabled workspace hooks. The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-41355 since 04/20/2026. The exploitation is known to be easy. An attack has to be approached locally. Neither technical details nor an exploit are publicly available. Upgrading to version 2026.3.28 eliminates this vulnerability. Applying the patch c02ee8a3a4cb390b23afdf21317aa8b2096854d1 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version. Productinfo Type Artificial Intelligence Software Name OpenClaw Version 2026.3.0 2026.3.1 2026.3.2 2026.3.3 2026.3.4 2026.3.5 2026.3.6 2026.3.7 2026.3.8 2026.3.9 2026.3.10 2026.3.11 2026.3.12 2026.3.13 2026.3.14 2026.3.15 2026.3.16 2026.3.17 2026.3.18 2026.3.19 2026.3.20 2026.3.21 2026.3.22 2026.3.23 2026.3.24 2026.3.25 2026.3.26 2026.3.27 License open-source Website Product: https://github.com/openclaw/openclaw/ CPE 2.3info 🔒 🔒 🔒 CPE 2.2info 🔒 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA CVSS-B Score: 🔒 CNA CVSS-BT Score: 🔒 CNA Vector: 🔒 CVSSv3info VulDB Meta Base Score: 6.3 VulDB Meta Temp Score: 6.2 VulDB Base Score: 5.3 VulDB Temp Score: 5.1 VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA Base Score: 7.3 CNA Vector (VulnCheck): 🔒 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Inclusion of functionality from untrusted control sphere CWE: CWE-829 CAPEC: 🔒 ATT&CK: 🔒 Physical: Partially Local: Yes Remote: Partially Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: OpenClaw 2026.3.28 Patch: c02ee8a3a4cb390b23afdf21317aa8b2096854d1 Timelineinfo 04/20/2026 CVE reserved 04/24/2026 +4 days Advisory disclosed 04/24/2026 +0 days VulDB entry created 04/24/2026 +0 days VulDB entry last update Sourcesinfo Product: github.com Advisory: GHSA-42mx-vp8m-j7qh Status: Confirmed CVE: CVE-2026-41355 (🔒) GCVE (CVE): GCVE-0-2026-41355 GCVE (VulDB): GCVE-100-359309 Entryinfo Created: 04/24/2026 08:01 Changes: 04/24/2026 08:01 (77) Complete: 🔍 Cache ID: 99:EE9:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸