Skip to main content

Openclaw CVE-2026-35639

| EUVDEUVD-2026-21134 HIGH
Incorrect Use of Privileged APIs (CWE-648)
2026-04-09 VulnCheck GHSA-hf68-49fm-59cq
8.7
CVSS 4.0 · NVD
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate as operator.pairing approver
  2. Delivery
    Call device.pair.approve method
  3. Exploit
    Bypass scope validation checks
  4. Execution
    Approve request with operator.admin scope
  5. Persist
    Escalate privileges to administrator
  6. Impact
    Execute arbitrary code on Node infrastructure

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V6 - Authentication Incorrect use of privileged APIs
Exploitation Conditions

OpenClaw before 2026.3.22: Attacker must hold operator.pairing approver role. Exploit the device.pair.approve method to approve pending device requests, escalating privileges to operator.admin. Requires network access to OpenClaw Node infrastructure.

Impact

Authenticated privilege escalation to admin with RCE on Node infrastructure. CVSS 8.7 reflects high confidentiality, integrity, and availability impact. Network-accessible attack with low complexity demands immediate patching. Patch availability reduces urgency slightly, but operator-held credentials enable lateral movement within trusted device-pairing workflows.

Exploit ScenarioDerived

Authenticated operator.pairing approver calls device.pair.approve method with crafted scope parameter exceeding their permissions, escalating to operator.admin. Attacker then executes arbitrary code on Node infrastructure via admin access. No public exploit identified at time of analysis.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Apr 09, 2026

Privilege escalation in OpenClaw before 2026.3.22 enables authenticated attackers with operator.pairing approver role to escalate privileges to operator.admin through insufficient scope validation in the device.pair.approve method. Exploitation allows approval of device requests with broader operator scopes than the approver legitimately holds, ultimately enabling remote code execution on Node infrastructure. Affects OpenClaw deployments where role-based access control enforces operator privilege hierarchies. No public exploit identified at time of analysis.

RemediationAI

Vendor-released patch: upgrade to OpenClaw version 2026.3.22 or later, which implements proper scope validation in device pairing approval workflows. Upstream fixes available via GitHub commits 630f1479c44f78484dfa21bb407cbe6f171dac87 and fc2d29ea926f47c428c556e92ec981441228d2a4. Temporary mitigation: restrict operator.pairing approver role assignments to only operators who already hold operator.admin privileges, effectively neutralizing the escalation path until patching. Review audit logs for suspicious device pairing approvals where granted scopes exceed approver permissions. Advisory: https://github.com/openclaw/openclaw/security/advisories/GHSA-hf68-49fm-59cq

Affected VersionsENISA

OpenClaw 0 <2026.3.22

Affected Packages

npm openclaw fix: 2026.3.22

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in npm

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

CWE-648 scope validation failure permits horizontal privilege escalation through device pairing workflow. The device.pair.approve method fails to verify that requested operator scopes remain within the approver's granted scope boundaries, allowing lateral movement from operator.pairing to operator.admin. Exploitation chain terminates in RCE against Node.js runtime infrastructure.

Know when Openclaw gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 8.7 HIGH
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

2
Patch released
Apr 09, 2026 - 21:45 nvd
Patch available
CVE Published
Apr 09, 2026 - 21:27 nvd
HIGH 8.7

DescriptionCVE.org

OpenClaw before 2026.3.22 contains a privilege escalation vulnerability in the device.pair.approve method that allows an operator.pairing approver to approve pending device requests with broader operator scopes than the approver actually holds. Attackers can exploit insufficient scope validation to escalate privileges to operator.admin and achieve remote code execution on the Node infrastructure.

Blast Radius

ecosystem impact
† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth
  • 5 npm packages depend on openclaw (5 direct, 0 indirect)

Ecosystem-wide dependent count for version 2026.3.22.

Executive ViewAI

Why It Matters

OpenClaw versions before 2026.3.22 contain a privilege escalation vulnerability allowing authenticated operators with pairing approval rights to escalate to administrative privileges, potentially enabling unauthorized remote code execution on Node infrastructure. Organizations running affected OpenClaw deployments face compromise of their operator access controls and infrastructure security posture. Immediate patching is required to restore proper authorization boundaries.

Business Impact: High
Compensating Controls

Apply vendor patch. If immediate patching is not feasible, restrict the operator.pairing approver role to trusted personnel only, disable device pairing workflows where operationally possible, and implement enhanced logging and alerting on device.pair.approve method calls and operator privilege changes.

Threat Intelligence Overview

EPSS Score
0.2%
Top 58% exploitable
Threat Intel
1
1 source
Data Quality
7 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment GHSA CIRCL GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

44
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +44
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

CVE-2026-28446 CRITICAL POC
9.4 Mar 05

Auth bypass in OpenClaw voice-call extension before 2026.2.1. EPSS 0.68%. PoC and patch available.

CVE-2026-33579 CRITICAL POC
9.4 Mar 31

Privilege escalation in OpenClaw (pre-2026.3.28) allows unauthenticated remote attackers to gain administrative access b

CVE-2026-32042 HIGH POC
8.8 Mar 21

OpenClaw versions 2026.2.22 through 2026.2.24 contain a privilege escalation vulnerability that allows authenticated att

CVE-2026-32051 HIGH POC
8.8 Mar 21

An authorization mismatch vulnerability in OpenClaw versions prior to 2026.3.1 allows authenticated users with operator.

CVE-2026-25253 HIGH POC
8.8 Feb 01

OpenClaw versions prior to 2026.1.29 automatically establish WebSocket connections to attacker-controlled gateway URLs e

CVE-2026-32846 HIGH POC
8.7 Mar 26

Path traversal in OpenClaw through version 2026.3.23 enables unauthenticated remote attackers to read arbitrary files in

CVE-2026-53857 HIGH POC
8.6 Jun 16

Authentication bypass in OpenClaw before 2026.5.3 allows remote attackers with low privileges to receive agent responses

CVE-2026-100530 HIGH POC
8.5 Sep 26

Directory-context bypass in OpenClaw before 2026.8.1 allows authenticated attackers with user interaction to reuse an 'a

CVE-2026-32064 HIGH POC
8.5 Mar 21

Unauthenticated access to the noVNC observer interface in OpenClaw's Docker sandbox browser allows anyone who can reach

CVE-2026-32055 HIGH POC
7.6 Mar 21

OpenClaw versions before 2026.2.26 allow authenticated attackers to write arbitrary files outside the workspace director

CVE-2026-32056 HIGH POC
7.5 Mar 21

OpenClaw versions prior to 2026.2.22 contain a shell environment variable injection vulnerability in the system.run func

CVE-2026-32049 HIGH POC
7.5 Mar 21

OpenClaw versions prior to 2026.2.22 contain a resource exhaustion vulnerability where the application fails to consiste

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy