OpenClaw: QQBot native approval buttons did not enforce configured approver identity (CVE-2026-35630)
### 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.
AI Analysis
Technical Summary
OpenClaw's QQBot channel delivers native approval buttons for exec and plugin approvals. In affected versions prior to 2026.5.18, the button callback path did not enforce the configured approver identity, allowing non-approver QQ users who could view approval messages to resolve pending requests by clicking approval buttons. The text command approval path correctly enforced authorization checks, so the vulnerability is limited to native QQBot approval buttons. This could lead to unauthorized execution of actions that should require an authorized approver.
Potential Impact
A non-authorized QQ user who can see an approval message can resolve pending exec or plugin approval requests by clicking the native approval button. This bypasses the intended authorization controls and may allow execution of privileged actions without proper approval.
Mitigation Recommendations
Upgrade OpenClaw to version 2026.5.18 or later, where this issue is fixed. Until the upgrade is applied, avoid delivering native approval buttons in QQ conversations that include users who are not authorized approvers.
OpenClaw: QQBot native approval buttons did not enforce configured approver identity (CVE-2026-35630)
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.
CVSS v4.0
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
OpenClaw's QQBot channel delivers native approval buttons for exec and plugin approvals. In affected versions prior to 2026.5.18, the button callback path did not enforce the configured approver identity, allowing non-approver QQ users who could view approval messages to resolve pending requests by clicking approval buttons. The text command approval path correctly enforced authorization checks, so the vulnerability is limited to native QQBot approval buttons. This could lead to unauthorized execution of actions that should require an authorized approver.
Potential Impact
A non-authorized QQ user who can see an approval message can resolve pending exec or plugin approval requests by clicking the native approval button. This bypasses the intended authorization controls and may allow execution of privileged actions without proper approval.
Mitigation Recommendations
Upgrade OpenClaw to version 2026.5.18 or later, where this issue is fixed. Until the upgrade is applied, avoid delivering native approval buttons in QQ conversations that include users who are not authorized approvers.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-mgq6-vr84-7m2j
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-35630"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- HIGH
- Cvss Version
- 4.0
Threat ID: 6a46ecae27e9c7971943b8ce
Added to database: 07/02/2026, 22:56:46 UTC
Last enriched: 07/02/2026, 23:05:23 UTC
Last updated: 07/31/2026, 19:22:58 UTC
Views: 32
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.