CVE-2026-35635 | OpenClaw up to 2026.3.21 Configuration name resolution (GHSA-rqp8-q22p-5j9q)

VDB-356779 · CVE-2026-35635 · GHSA-RQP8-Q22P-5J9Q OPENCLAW UP TO 2026.3.21 CONFIGURATION NAME RESOLUTION HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 5.1 $0-$5k 1.21+ Summaryinfo A vulnerability has been found in OpenClaw up to 2026.3.21 and classified as problematic. Impacted is an unknown function of the component Configuration Handler. This manipulation causes name resolution. The identification of this vulnerability is CVE-2026-35635. It is possible to initiate the attack remotely. There is no exploit available. The affected component should be upgraded. Detailsinfo A vulnerability classified as problematic was found in OpenClaw up to 2026.3.21. Affected by this vulnerability is an unknown part of the component Configuration Handler. The manipulation with an unknown input leads to a name resolution vulnerability. The CWE definition for the vulnerability is CWE-706. The product uses a name or reference to access a resource, but the name/reference resolves to a resource that is outside of the intended control sphere. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is: OpenClaw before 2026.3.22 contains a webhook path route replacement vulnerability in the Synology Chat extension that allows attackers to collapse multi-account configurations onto shared webhook paths. Attackers can exploit inherited or duplicate webhook paths to bypass per-account DM access control policies and replace route ownership across accounts. It is possible to read the advisory at github.com. This vulnerability is known as CVE-2026-35635 since 04/04/2026. The exploitation appears to be difficult. The attack can be launched remotely. The exploitation doesn't need any form of authentication. The technical details are unknown and an exploit is not publicly available. Upgrading to version 2026.3.22 eliminates this vulnerability. Applying the patch 630f1479c44f78484dfa21bb407cbe6f171dac87 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 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: 5.2 VulDB Meta Temp Score: 5.1 VulDB Base Score: 5.6 VulDB Temp Score: 5.4 VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA Base Score: 4.8 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: Name resolution CWE: CWE-706 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Yes 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.22 Patch: 630f1479c44f78484dfa21bb407cbe6f171dac87 Timelineinfo 04/04/2026 CVE reserved 04/10/2026 +6 days Advisory disclosed 04/10/2026 +0 days VulDB entry created 04/10/2026 +0 days VulDB entry last update Sourcesinfo Product: github.com Advisory: GHSA-rqp8-q22p-5j9q Status: Confirmed CVE: CVE-2026-35635 (🔒) GCVE (CVE): GCVE-0-2026-35635 GCVE (VulDB): GCVE-100-356779 Entryinfo Created: 04/10/2026 06:54 Changes: 04/10/2026 06:54 (78) Complete: 🔍 Cache ID: 99:E8D:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸