CVE-2026-35630: OpenClaw < 2026.5.18 - QQBot Missing Approver Identity Enforcement in Native Approval Buttons
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.
Other sources
OpenClaw before 2026.5.18 contains an authorization bypass vulnerability in QQBot native approval buttons that fails to enforce configured approver identity. Non-approver users can click approval buttons to resolve pending exec or plugin approval requests without proper authorization.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
npm/openclawto a version that resolves this vulnerability.Fixed in 2026.5.18 - Upgrade
Upgrade
openclawto a version that resolves this vulnerability.Fixed in 2026.5.18 - Configuration
Before upgrading, avoid delivering native approval buttons into QQ conversations that include users who should not be able to approve.
OpenClaw QQBot native approval buttons for exec/plugin approvals = disable (avoid delivering native approval buttons into QQ conversations that include users who should not be able to approve)
Event History
Frequently Asked Questions
What is the severity of CVE-2026-35630?
The severity of CVE-2026-35630 is high, with a CVSS score of 7.5.
How do I fix CVE-2026-35630?
To fix CVE-2026-35630, upgrade OpenClaw to version 2026.5.18 or later.
What is the impact of CVE-2026-35630?
CVE-2026-35630 allows non-approver users to bypass authorization and approve requests without proper permissions.
Which software is affected by CVE-2026-35630?
CVE-2026-35630 affects OpenClaw versions prior to 2026.5.18.
Is user interaction required for CVE-2026-35630 exploitation?
Yes, user interaction is required for exploitation of CVE-2026-35630 because it involves clicking native approval buttons.