Threats Tagged 'cve-2026-35630'
View all threats tagged with 'cve-2026-35630'. Filter and sort to focus on specific types of threats.
Stop chasing alerts. Route them.
Start free, then upgrade once to turn Radar into an automated delivery engine for your security stack.
Custom feeds / Automations: email, Slack, webhooks, SIEM/MISP / API access (baseline limits)
API access activates after upgrading in Console -> Billing.
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.
Filter Threats
Narrow down the results by type, severity, or affected countries
Threats Tagged 'cve-2026-35630'
Click on any threat for detailed analysis and mitigation recommendations
OpenClaw: QQBot native approval buttons did not enforce configured approver identity (CVE-2026-35630)CVE-2026-35630 0 ### 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. Join the discussion | GCVE Database | 07/02/2026, 16:05:20 UTC Added: 07/02/2026, 22:56:46 UTC |
Showing 1 to 1 of 1 result