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

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

OpenClaw EUVD-2026-25275

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

EUVD-2026-25275 has a CVSS 4.0 base score of 5.3 (Medium). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/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-41909 MEDIUM

Incorrect Authorization (CWE-863)

2026-04-23 VulnCheck

GHSA-qrrm-x53p-gpw4

Authentication Bypass Openclaw

5.3

CVSS 4.0 · NVD

Severity by source

NVD PRIMARY

5.3 MEDIUM

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

5.4 MEDIUM

Requires prior device-token authentication (PR:L); limited to pairing state enumeration and management within the same gateway (C:L/I:L); no availability or scope impact.

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

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

Primary rating from NVD.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

Source Code Evidence Fetched

Jul 24, 2026 - 04:39 vuln.today

Analysis Generated

Jul 24, 2026 - 04:39 vuln.today

CVSS changed

Apr 23, 2026 - 18:42 NVD

5.4 (MEDIUM) 5.3 (MEDIUM)

EUVD ID Assigned

Apr 23, 2026 - 18:15 euvd

EUVD-2026-25275

Patch released

Apr 23, 2026 - 18:15 nvd

Patch available

CVE Published

Apr 23, 2026 - 17:52 nvd

MEDIUM 5.3

DescriptionCVE.org

OpenClaw before 2026.4.20 contains an improper authorization vulnerability in paired-device pairing management that allows limited-scope sessions to enumerate and act on pairing requests. Attackers with paired-device access can approve or operate on unrelated pending device requests within the same gateway scope.

AnalysisAI

Improper authorization in OpenClaw's paired-device pairing management (npm package, versions before 2026.4.20) allows authenticated paired devices with limited operator.pairing scope to enumerate global pairing state and approve or reject pending device requests belonging to other devices within the same gateway scope. This is a same-gateway, authenticated privilege escalation bug - not a remote unauthenticated issue. No public exploit code exists and CISA has not listed this in KEV; SSVC assesses exploitation as none and technical impact as partial, consistent with the low EPSS score of 0.03%.

Technical ContextAI

OpenClaw is an npm-distributed IoT/device gateway library (CPE: cpe:2.3:a:openclaw:openclaw:*:*:*:*:*:*:*:*) that manages paired-device sessions through a scope-based authorization model. The gateway exposes server-side methods (device.pair.list, approve, reject, get) in src/gateway/server-methods/devices.ts. CWE-863 (Incorrect Authorization) applies: the system correctly required the operator.pairing scope for pairing actions but failed to differentiate between device-token authenticated sessions (non-admin paired devices) and admin or shared-secret operator sessions. As a result, any valid device-token session holding operator.pairing scope could call gateway-wide pairing APIs, receiving and acting upon pairing requests scoped to other devices. The fix introduced an isDeviceTokenAuth flag on the client session object, enabling the handler to filter list/approve/reject results to only the calling device unless the session also holds operator.admin.

RemediationAI

Upgrade the openclaw npm package to version 2026.4.20 or later, which restricts non-admin paired-device sessions to their own pairing list, approve, and reject actions. The fix is implemented in commit 5a12f30441d5b0b151f550daa2c5c9e8db61e2e6 and is confirmed released in the 2026.4.20 package. The vendor advisory is at https://github.com/openclaw/openclaw/security/advisories/GHSA-xrq9-jm7v-g9h7. If immediate upgrade is not possible, a compensating control is to restrict device sessions to a single trusted device per gateway scope, eliminating cross-device enumeration risk; however, this may disrupt multi-device deployment architectures. Admin and shared-secret operator sessions retain full pairing visibility by design in the patched version.