Summary
OpenClaw: /pair approve command path omitted caller scope subsetting and reopened device pairing escalation
The /pair approve command path called device approval without forwarding caller scopes into the core approval check.
Affected Component
extensions/device-pair/index.ts, src/infra/device-pairing.ts
Fixed Versions
- Affected:
<= 2026.3.24 - Patched:
>= 2026.3.28 - Latest stable
2026.3.28contains the fix.
Impact
A caller that held pairing privileges but not admin privileges could approve a pending device request asking for broader scopes, including admin access.
The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Fixed by commit 4ee4960de2 (Pairing: forward caller scopes during approval).
OpenClaw thanks @AntAISecurityLab for reporting.
Frequently Asked Questions
- What is CVE-2026-33579? CVE-2026-33579 is a critical-severity incorrect authorization vulnerability in openclaw (npm), affecting versions <= 2026.3.24. It is fixed in 2026.3.28. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
- Which versions of openclaw are affected by CVE-2026-33579? openclaw (npm) versions <= 2026.3.24 is affected.
- Is there a fix for CVE-2026-33579? Yes. CVE-2026-33579 is fixed in 2026.3.28. Upgrade to this version or later.
- Is CVE-2026-33579 exploitable, and should I be worried? Whether CVE-2026-33579 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-33579 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-33579? Upgrade
openclawto 2026.3.28 or later.