CVE-2026-33579 Details
Description
OpenClaw before 2026.3.28 contains a privilege escalation vulnerability in the /pair approve command path that fails to forward caller scopes into the core approval check. A caller with pairing privileges but without admin privileges can approve pending device requests asking for broader scopes including admin access by exploiting the missing scope validation in extensions/device-pair/index.ts and src/infra/device-pairing.ts.
A privilege escalation vulnerability has been identified in OpenClaw versions prior to 2026.3.28. The issue arises in the '/pair approve' command path, where the application fails to properly validate and forward caller scopes during the approval process. This oversight allows users with pairing privileges, but not admin rights, to approve device requests that require broader scopes, including admin access. The vulnerability is present in the 'extensions/device-pair/index.ts' and 'src/infra/device-pairing.ts' components.
Users can update to OpenClaw version 2026.3.28 or later, where this vulnerability has been patched.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Apr 1, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-863 | Incorrect Authorization | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| openclaw openclaw | < 2026.3.28 |
CPE
Remediation
| |
Change History
7 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jul 24, 2026 | CVE Translated | [email protected] |
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Apr 6, 2026 | CVE Modified | [email protected] |
| Apr 1, 2026 | Initial Analysis | [email protected] |
| Mar 31, 2026 | CVE Modified | [email protected] |
| Mar 31, 2026 | New CVE Received | [email protected] |