Is there a patch available for EUVD-2026-36623?

Yes, a patch is available for EUVD-2026-36623. Update the affected software to the latest version immediately.

OpenClaw EUVD-2026-36623

Q: What is the CVSS score of EUVD-2026-36623?

EUVD-2026-36623 has a CVSS 4.0 base score of 2.3 (Low). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/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. EPSS exploitation probability: 0.0%.

| CVE-2026-53835 LOW

Incorrect Authorization (CWE-863)

2026-06-12 VulnCheck

GHSA-gjr2-gw52-3xch

Authentication Bypass Openclaw

2.3

CVSS 4.0 · Vendor: VulnCheck

Severity by source

Vendor (VulnCheck) PRIMARY

2.3 LOW

CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/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

vuln.today AI

3.1 LOW

AT:P (Feishu dynamic-agent binding must be configured) maps to AC:H; PR:L reflects required authenticated sender; strictly integrity-only impact with no scope change.

3.1 AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N

4.0 AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

Patch available

Jun 13, 2026 - 02:00 EUVD

Analysis Generated

Jun 12, 2026 - 22:44 vuln.today

Blast Radius

ecosystem impact

† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth

1 npm packages depend on openclaw (1 direct, 0 indirect)

Ecosystem-wide dependent count for version 2026.5.6.

DescriptionCVE.org

OpenClaw before 2026.5.6 contains a configuration enforcement bypass vulnerability in Feishu dynamic-agent bindings that allows authenticated senders to create or update bindings without honoring configured config-write controls. Attackers can exploit this by leveraging the dynamic-agent binding feature to change sender-agent binding state beyond intended policy, potentially enabling unauthorized binding modifications.

AnalysisAI

Configuration enforcement bypass in OpenClaw's Feishu dynamic-agent binding subsystem permits authenticated senders to create or update sender-agent bindings while circumventing configured config-write access controls. All OpenClaw versions prior to 2026.5.6 are affected; an attacker holding valid sender credentials can modify binding state beyond intended policy, potentially redirecting or hijacking agent associations belonging to other users. No public exploit code exists and this vulnerability is not listed in the CISA KEV catalog; the CVSS 4.0 score of 2.3 reflects the narrow impact scope and prerequisite deployment conditions.

Technical ContextAI

OpenClaw is a messaging and agent-routing platform that integrates with Feishu (Lark) through a dynamic-agent binding mechanism, which maps sender identities to specific agents for message routing. The vulnerability is rooted in CWE-863 (Incorrect Authorization): the authorization layer governing write operations on these bindings fails to enforce its own config-write control policy when processing binding creation or update requests from authenticated senders. The affected product surface is fully described by CPE cpe:2.3:a:openclaw:openclaw:*:*:*:*:*:*:*:*, covering all releases before the 2026.5.6 fix. The CVSS 4.0 AT:P metric (Attack Requirements: Present) directly captures the precondition that the Feishu dynamic-agent binding feature must be configured and actively in use for the vulnerable code path to be reachable.

RemediationAI

Upgrade OpenClaw to version 2026.5.6 or later; this is the vendor-released patch that resolves the authorization bypass, as confirmed by the GitHub security advisory GHSA-3wqp-prf6-2m72 at https://github.com/openclaw/openclaw/security/advisories/GHSA-3wqp-prf6-2m72. For environments that cannot patch immediately, administrators should audit and tightly restrict which authenticated sender accounts hold any access to the Feishu dynamic-agent binding feature, reducing the pool of accounts that could exploit the unenforced policy - note this does not eliminate the vulnerability but raises the bar by limiting exposure to fewer principals. If the Feishu dynamic-agent integration is not operationally required, disabling the feature entirely removes the attack surface with no side effects beyond interrupting dynamic binding-based routing for affected senders.