Is there a public PoC exploit available for EUVD-2026-37152?

Yes, a public proof-of-concept exploit is available for EUVD-2026-37152. Prioritise patching immediately. EPSS: 0.1%.

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

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

OpenClaw EUVD-2026-37152

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

EUVD-2026-37152 has a CVSS 4.0 base score of 6.8 (Medium). CVSS vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/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.1%.

| CVE-2026-53850 MEDIUM

Missing Authorization (CWE-862)

2026-06-16 VulnCheck

GHSA-gw2c-6hcg-5g52

GHSA-mpc8-jxjh-qpgh

Authentication Bypass Openclaw

6.8

CVSS 4.0 · Vendor: VulnCheck

Severity by source

Vendor (VulnCheck) PRIMARY

6.8 MEDIUM

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

5.5 MEDIUM

Local attack vector and low-privilege authentication required per description and CVSS 4.0 input; integrity-only high impact with no scope change, confidentiality, or availability effect.

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

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

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

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

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

Patch available

Jun 16, 2026 - 20:02 EUVD

Analysis Generated

Jun 16, 2026 - 19:04 vuln.today

DescriptionCVE.org

OpenClaw before 2026.4.25 contains a control scope enforcement bypass vulnerability in the focus command that allows authenticated callers to execute the command without proper authorization checks. Attackers can trigger the focus command to change focus state outside intended caller authority, potentially enabling unauthorized operations depending on gateway configuration and input trust levels.

AnalysisAI

OpenClaw before version 2026.4.25 permits authenticated local callers to invoke the focus command without passing proper authorization checks, enabling control scope enforcement bypass (CWE-862: Missing Authorization). Any low-privileged local user can alter focus state outside their intended caller authority, with downstream impact varying by gateway configuration and input trust levels. No public exploit code has been identified and this vulnerability is not listed in the CISA KEV catalog at time of analysis.

Technical ContextAI

OpenClaw is a software product (CPE: cpe:2.3:a:openclaw:openclaw:*:*:*:*:*:*:*:*) that exposes a command-based control interface including a 'focus command' mechanism. The root cause is CWE-862 (Missing Authorization): the focus command handler executes without verifying that the invoking caller holds the appropriate authority or scope permissions. This is a control plane enforcement failure - the command logic itself functions as designed, but the gatekeeping layer that restricts which callers may trigger it is absent or bypassable. The CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N) confirms that exploitation is constrained to local, low-privilege access with a high integrity impact to the vulnerable system and no subsequent-system effect, ruling out network-based or unauthenticated exploitation paths.

RemediationAI

The primary fix is to upgrade OpenClaw to version 2026.4.25 or later, which resolves the missing authorization check in the focus command per the vendor security advisory at https://github.com/openclaw/openclaw/security/advisories/GHSA-mpc8-jxjh-qpgh. If immediate patching is not feasible, restrict local system access and the OpenClaw command interface to only those accounts that legitimately require focus command authority, reducing the pool of low-privilege callers who can abuse this bypass - note this is a compensating control only and does not remediate the root flaw. Additionally, review and harden gateway configuration and input trust level settings referenced in the vulnerability description, as these directly govern the operational impact of exploitation in a given deployment. Tightening trust boundaries at the gateway layer can reduce the radius of unauthorized operations even if the authorization bypass is triggered.