Is CVE-2026-35639 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-35639 being exploited in the wild.

How severe is CVE-2026-35639?

Critical severity, with a CVSS score of 4, published 26 March 2026.

Which products and versions are affected?

openclaw (npm) SEMVER:introduced=0,fixed=2026.3.22; Openclaw < 2026.3.22.

Is there a fix for CVE-2026-35639?

Yes. openclaw (npm): upgrade to 2026.3.22 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-35639 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-35639?

Check whether you run openclaw (npm) or Openclaw at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-35639: OpenClaw Gateway privilege escalation in device.pair.approve

Q: Is there a fix for CVE-2026-35639?

Yes. openclaw (npm): upgrade to 2026.3.22 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-35639 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-35639?

Check whether you run openclaw (npm) or Openclaw at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-35639 · Severity: critical · CVSS 4 · Published 2026-03-26

OpenClaw Gateway, a tool used for managing device connections, contains a security flaw in its device approval process. An attacker with low-level pairing permissions can approve device requests with full administrative privileges, effectively taking over the gateway. This could lead to unauthorized access to sensitive data, service disruption, or complete system compromise.

Technologies: openclaw (npm), Openclaw. Vendors: npm, Openclaw.

Quick answers

Is CVE-2026-35639 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-35639 being exploited in the wild.
How severe is CVE-2026-35639?: Critical severity, with a CVSS score of 4, published 26 March 2026.
Which products and versions are affected?: openclaw (npm) SEMVER:introduced=0,fixed=2026.3.22; Openclaw < 2026.3.22.
Is there a fix for CVE-2026-35639?: Yes. openclaw (npm): upgrade to 2026.3.22 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-35639 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-35639?: Check whether you run openclaw (npm) or Openclaw at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

openclaw (npm): upgrade to 2026.3.22 or later
```
npm install openclaw@2026.3.22
```

Technical details

A privilege management vulnerability (CWE-269) exists in OpenClaw Gateway's 'device.pair.approve' method. The root cause is a failure to validate that the requested scopes for a new device do not exceed the scopes held by the approving operator. An attacker with 'operator.pairing' permissions can approve a pending device request and grant it 'operator.admin' scopes. This escalation can lead to Remote Code Execution (RCE) and full system compromise. The fix, introduced in version 2026.3.22, ensures that caller scopes are threaded into the approval logic and that requested scopes exceeding the approver's set are rejected.

Affected products

OpenClaw openclaw < 2026.3.22

Identifiers

CVE-2026-35639
GHSA-hf68-49fm-59cq

Timeline

2026-03-24: disclosed: Initial disclosure in openclaw/openclaw repository
2026-03-26: advisory: GitHub Advisory published
2026-03-22: patched: Fix released in version 2026.3.22

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.