Authorization Bypass in OpenClaw: QQBot Native Approval Buttons Vulnerability

openclaw Updated 03 Jul 2026

Summary

29/05/2026
HIGH
Yes i
High
8.0

GHSA-hx4v-668p-g2qr: Duplicate Advisory This advisory has been withdrawn because it is a duplicate of GHSA-mgq6-vr84-7m2j. Affects openclaw versions < 2026.5.18. Fixed in 2026.5.18. 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 Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

OpenClaw is an open-source framework designed for building and managing bots, particularly in environments where automated approvals are necessary. It allows users to configure approval workflows for various actions, such as executing commands or approving plugins. However, prior to version 2026.5.18, OpenClaw had a significant vulnerability that could allow unauthorized users to bypass approval mechanisms, compromising the integrity of the approval process.

Vulnerability Detail

The vulnerability in OpenClaw arises from an authorization bypass in the QQBot native approval buttons. This flaw allows non-approver users to click on approval buttons, thereby resolving pending execution or plugin approval requests without the necessary authorization. The issue stems from the failure to enforce the configured approver identity, which could lead to unauthorized actions being taken within the system, potentially resulting in severe security implications.

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.5.18

This is the first release that contains the fix.

npm install openclaw@2026.5.18

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

Workaround

As a temporary workaround, you can restrict access to the approval buttons by implementing additional checks in your application logic to ensure that only authorized users can interact with these buttons. However, this is not a permanent solution and should be replaced with the official patch as soon as possible.

Conclusion

In summary, the OpenClaw vulnerability related to QQBot native approval buttons poses a significant security risk due to an authorization bypass. Users are strongly advised to update to version 2026.5.18 or later to mitigate this risk. Implementing additional access controls can serve as a temporary workaround, but the official patch is the best long-term solution.

See every vulnerability recorded for openclaw →

Share this vulnerability

FAQ

The CVSS score of this vulnerability is 8.0, indicating a high severity level.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground at Vulert Scanner without any signup.

The risks include unauthorized actions being taken within the system, which could lead to data breaches, execution of malicious commands, or unauthorized plugin installations.

While the best solution is to update, you can implement additional access controls to limit who can interact with approval buttons as a temporary measure.

If immediate updating is not possible, ensure that you have strict access controls in place and monitor your application for any unauthorized activities.

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.5.18

This is the first release that contains the fix.

npm install openclaw@2026.5.18

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

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.