CVE-2026-34507
Policy Bypass in OpenClaw QQBot Admin Commands
Publication date: 2026-05-29
Last updated on: 2026-05-29
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| openclaw | openclaw | to 2026.4.29 (exc) |
| qqbot | qqbot | to 2026.4.29 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-863 | The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-34507 is a policy bypass vulnerability in OpenClaw versions before 2026.4.29 affecting QQBot admin commands. It allows authenticated users to bypass DM-only and allowFrom policy checks, which are intended to restrict who can execute certain admin commands.
Because of this flaw, attackers can route admin commands from unauthorized senders or contexts, enabling them to perform restricted actions that should have been blocked by the policy.
How can this vulnerability impact me? :
This vulnerability can allow an attacker with authenticated access to execute admin commands from unauthorized senders or contexts, potentially leading to unauthorized administrative actions.
The practical impact depends on the operator's configuration and whether lower-trust inputs can reach the vulnerable QQBot admin command path.
Mitigations include disabling exported QQBot admin commands or restricting QQBot access until the patch is applied. General security hardening such as narrowing channel and tool allowlists and avoiding shared Gateways between untrusted users can reduce risk.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should upgrade OpenClaw to version 2026.4.29 or later, where the issue is patched.
If upgrading immediately is not possible, you can disable exported QQBot admin commands or restrict QQBot access until the patch is applied.
Additional hardening steps include keeping channel and tool allowlists narrow, avoiding shared Gateways between untrusted users, and disabling the affected feature when it is not needed.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows authenticated attackers to bypass policy checks and execute restricted admin commands from unauthorized senders or contexts. This could potentially lead to unauthorized access or actions within the system.
However, the practical impact depends on the operator's configuration and whether lower-trust input can reach the affected feature. Mitigations include disabling the vulnerable feature or restricting access until patched.
There is no explicit information provided about how this vulnerability directly affects compliance with common standards and regulations such as GDPR or HIPAA.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability involves a policy bypass in QQBot admin commands allowing authenticated senders to skip DM-only and allowFrom policy checks. Detection involves monitoring for unauthorized execution of QQBot admin commands from senders or contexts that should be blocked by these policies.
Suggested detection methods include:
- Review logs for QQBot admin command executions originating from unexpected or unauthorized senders or contexts.
- Check for usage of admin commands outside of direct messages (DMs) or from sources not included in the allowFrom policy.
- If possible, use network monitoring tools to detect unusual command traffic patterns related to QQBot admin commands.
Specific commands depend on your environment and logging setup, but examples might include searching logs with commands like:
- grep or similar tools to find admin command usage in logs, e.g., `grep "admin_command" /var/log/qqbot.log`
- Filtering logs for commands executed outside of DMs or from unauthorized users, e.g., `grep -E "admin_command" /var/log/qqbot.log | grep -v "DM"`
Additionally, monitoring for unexpected QQBot admin command activity and restricting or disabling exported QQBot admin commands until patched can help mitigate risk.