---
id: GHSA-mgq6-vr84-7m2j
title: >-
  OpenClaw: QQBot native approval buttons did not enforce configured approver
  identity
summary: >-
  OpenClaw: QQBot native approval buttons did not enforce configured approver
  identity
severity: high
cvss: 8
cwe:
  - CWE-862
vendor: openclaw
product: openclaw
ecosystem: npm
affected:
  - openclaw < 2026.5.18
patched:
  - openclaw 2026.5.18
published: '2026-07-02'
updated: '2026-07-02'
source: GHSA
sourceUrl: 'https://github.com/advisories/GHSA-mgq6-vr84-7m2j'
references:
  - url: >-
      https://github.com/openclaw/openclaw/security/advisories/GHSA-mgq6-vr84-7m2j
  - url: 'https://github.com/advisories/GHSA-mgq6-vr84-7m2j'
tags:
  - ghsa
  - npm
ingestedAt: '2026-07-02T16:39:34.595Z'
---

## Overview

### Summary

OpenClaw's QQBot channel can deliver native approval buttons for exec and plugin approvals. In affected releases, the button callback path resolved approvals without enforcing the configured QQBot approver identity.

The text command approval path used the authorization check; the issue was specific to native QQBot approval buttons.

### Affected configurations

This affects deployments where QQBot native approval buttons are enabled and an approval message is visible to a QQ user who is not configured as an approver.

### Impact

A non-approver who could see the approval message could click an approval button and resolve the pending request. Depending on the pending approval, this could allow an exec or plugin action that should have required an authorized approver.

### Patched Versions

The first stable patched version is `2026.5.18`.

### Mitigations

Upgrade to `openclaw@2026.5.18` or later. Before upgrading, avoid delivering native approval buttons into QQ conversations that include users who should not be able to approve.

## Affected packages

- `openclaw < 2026.5.18`

## Remediation

Upgrade to a patched release:

- `openclaw 2026.5.18`