Unprivileged Pairing Approval in OpenClaw Package Vulnerability

openclaw Updated 09 Apr 2026

Summary

09/04/2026
MODERATE
Yes i
Moderate
6.9

GHSA-67mf-f936-ppxf: Impact OpenClaw node.pair.approve placed in operator.write scope instead of operator.pairing allows unprivileged pairing approval. Affects openclaw versions < 2026.4.8. Fixed in 2026.4.8. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

OpenClaw is a user-controlled local assistant designed to facilitate various tasks through a user-friendly interface. It allows users to manage their devices and services efficiently. However, a recent vulnerability has been identified that compromises its security model, specifically related to the pairing approval process.

Vulnerability Detail

The vulnerability arises from the node.pair.approve method being incorrectly placed in the operator.write scope instead of the more restrictive operator.pairing scope. This misconfiguration allows unprivileged users to approve pairing requests, potentially leading to unauthorized access and control over devices connected to the OpenClaw assistant. The issue is particularly concerning as it undermines the trust model of OpenClaw, which assumes a single-user environment without multi-tenant service boundaries.

How To Fix

Latest published version: 2026.10.6 as of 22 Oct 2026

npm install openclaw@2026.10.6

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2026.4.8

This is the first release that contains the fix.

npm install openclaw@2026.4.8

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

Currently, there are no specific workarounds mentioned for this vulnerability other than updating to the patched version. It is advisable to monitor the application for any unauthorized pairing attempts until the update is applied.

Conclusion

The OpenClaw package has a vulnerability that allows unprivileged pairing approval due to incorrect scope assignment. Users are advised to update to the patched version to mitigate this risk. Regular monitoring and using tools like Vulert can help ensure your application remains secure.

See every vulnerability recorded for openclaw →

Share this vulnerability

FAQ

The vulnerability allows unprivileged users to approve pairing requests due to a misconfiguration in the scope of the node.pair.approve method.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

The CVSS score of this vulnerability is 6.9, indicating a moderate severity level.

Yes, the vulnerability has been patched in version 2026.4.8 of the OpenClaw package.

If you cannot update the package immediately, monitor your application for any unauthorized pairing attempts and consider restricting access to the OpenClaw assistant until the update can be applied.

Related vulnerabilities

Recent vulnerabilities recorded for openclaw.

How To Fix

Latest published version: 2026.10.6 as of 22 Oct 2026

npm install openclaw@2026.10.6

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2026.4.8

This is the first release that contains the fix.

npm install openclaw@2026.4.8

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback