GitHub Advisoryadvisory · npm

GHSA-mgq6-vr84-7m2j OpenClaw: QQBot native approval buttons did not enforce configured approver identity

HIGH Published 2026-07-02 Modified 2026-07-02 Official page ↗
Aliases
CVE-2026-35630
Ecosystem
npm
Packages
openclaw
Severity
High
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
Weaknesses
CWE-862
Reviewed
2026-07-02

Affected packages

• npm openclaw: < 2026.5.18 → fixed in 2026.5.18

Description

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 `[email protected]` or later. Before upgrading, avoid delivering native approval buttons into QQ conversations that include users who should not be able to approve.

Related

Alias · CVE (1)

  • CVE-2026-35630 OpenClaw before 2026.5.18 contains an authorization bypass vulnerability in QQBot native approval buttons that fails to enforce configured… vulnerability

Weakness · CWE (1)

  • CWE-862 Missing Authorization weakness

References