Which versions of Openclaw are affected by EUVD-2026-17003?

OpenClaw versions before 2026.3.11 contain a privilege escalation vulnerability allowing authenticated operators to escalate their access to admin-level permissions, potentially enabling remote code…. A patch is available.

How to fix or mitigate EUVD-2026-17003?

Within 24 hours: Identify all OpenClaw instances and document current versions in use. Within 7 days: Apply vendor patch to upgrade all OpenClaw deployments to version 2026.3.11 or later; verify patch application across all nodes. Within 30 days: Audit operator.pairing scope assignments, revoke unnecessary operator access, and implement scope-based access control reviews; log and monitor system.run API calls for anomalies.

Openclaw EUVD-2026-17003

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

EUVD-2026-17003 has a CVSS 4.0 base score of 9.4 (Critical). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/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.2%.

| CVE-2026-32922 CRITICAL

Incorrect Privilege Assignment (CWE-266)

2026-03-29 VulnCheck

GHSA-x8qx-w8w2-g4rx

Privilege Escalation RCE Openclaw

9.4

CVSS 4.0 · NVD

Severity by source

NVD PRIMARY

9.4 CRITICAL

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Analysis Updated

Apr 16, 2026 - 05:47 EUVD-patch-fix

executive_summary

Re-analysis Queued

Apr 16, 2026 - 05:29 backfill_euvd_patch

patch_released

Patch available

Apr 16, 2026 - 05:29 EUVD

2026.3.11

EUVD ID Assigned

Mar 29, 2026 - 13:15 euvd

EUVD-2026-17003

Analysis Generated

Mar 29, 2026 - 13:15 vuln.today

CVE Published

Mar 29, 2026 - 12:44 nvd

CRITICAL 9.4

Blast Radius

ecosystem impact

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

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

Ecosystem-wide dependent count for version 2026.3.11.

DescriptionCVE.org

OpenClaw before 2026.3.11 contains a privilege escalation vulnerability in device.token.rotate that allows callers with operator.pairing scope to mint tokens with broader scopes by failing to constrain newly minted scopes to the caller's current scope set. Attackers can obtain operator.admin tokens for paired devices and achieve remote code execution on connected nodes via system.run or gain unauthorized gateway-admin access.

AnalysisAI

Privilege escalation in OpenClaw device token rotation (versions before 2026.3.11) enables authenticated attackers with operator.pairing scope to mint tokens with arbitrary elevated scopes, including operator.admin privileges. This scope validation bypass permits remote code execution on connected nodes via system.run API and unauthorized gateway-admin access. CVSS 9.4 (Critical) with network attack vector and low complexity. EPSS and KEV data not provided; no public exploit identified at time of analysis, though technical details disclosed via GitHub security advisory increase exploitation risk.

Technical ContextAI

This vulnerability affects the device.token.rotate API endpoint in OpenClaw, an apparent device management or IoT gateway platform. The root cause is improper privilege management (CWE-266) where the token minting function fails to validate that newly generated tokens inherit only the scope constraints of the requesting caller's current token. In role-based access control systems, scopes define authorization boundaries-operator.pairing should allow device registration, while operator.admin grants full administrative capabilities. The vulnerable code path permits scope escalation during token rotation, effectively breaking the principle of least privilege. The CPE identifier (cpe:2.3:a:openclaw:openclaw) indicates this affects the core OpenClaw application. The CVSS 4.0 vector shows network-accessible attack (AV:N), low complexity (AC:L), requiring only low-level privileges (PR:L) with no user interaction (UI:N), resulting in complete compromise of confidentiality, integrity, and availability across vulnerable and subsequent systems (VC:H/VI:H/VA:H/SC:H/SI:H/SA:H).

RemediationAI

Immediately upgrade OpenClaw to version 2026.3.11 or later, which implements proper scope constraint validation in the device.token.rotate function. The vendor-released patch is available through the GitHub security advisory at https://github.com/openclaw/openclaw/security/advisories/GHSA-4jpw-hj22-2xmc. Until patching is complete, implement network-level access controls to restrict device.token.rotate API calls to trusted internal networks only, and audit all existing operator.admin tokens to identify unauthorized escalations. Rotate all device tokens post-upgrade to ensure no attacker-minted elevated tokens persist. Review system.run API logs for suspicious remote command execution attempts. Organizations unable to immediately patch should consider temporarily disabling the token rotation endpoint if operationally feasible, though this may impact legitimate device pairing workflows. No compensating controls fully mitigate the vulnerability-upgrade to 2026.3.11 remains the only complete remediation.