CVE-2026-34507
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOpenClaw before 2026.4.29 contains a policy bypass vulnerability in QQBot admin commands that allows authenticated senders to skip DM-only and allowFrom policy checks. Attackers can route admin commands from unauthorized senders or contexts to execute restricted behavior that policy should have blocked.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceOpenClaw QQBot before 2026.4.29 has a policy bypass vulnerability in its admin command handling. The system implements DM-only and allowFrom policy checks to restrict certain admin commands, but authenticated senders can circumvent these checks by routing commands through unauthorized senders or contexts, allowing restricted behavior that should be blocked.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2026.4.29CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check OpenClaw versionLocate and inspect the OpenClaw installation directory or use a version query command if available (such as --version or checking version.json/runtime metadata). Compare the installed version string to 2026.4.29.Affected if Installed version is earlier than 2026.4.29 (e.g., 2026.4.28, 2026.4.0, etc.)
-
Verify QQBot module is enabledInspect the OpenClaw configuration files (such as config.yaml, modules.json, or similar) to confirm the QQBot plugin/module is loaded and active.Affected if QQBot module is present and enabled in the active configuration.
-
Examine admin command policy settingsLocate the QQBot admin command policy configuration (commonly in qqbot.yaml, admin_policy.json, or within the main config under an admin_commands or policies section). Specifically look for DM-only and allowFrom directive settings.Affected if DM-only is set to false, allowFrom contains wildcard values or missing sender restrictions, or policies appear to be improperly applied.
-
Review command execution logs for policy bypass indicatorsSearch command execution logs, audit trails, or bot activity logs for admin commands executed from non-DM contexts or from senders not listed in allowFrom rules.Affected if Admin commands appear in logs originating from group channels, unexpected sender IDs, or contexts that should have been blocked by existing policies.
The environment is affected if OpenClaw version is earlier than 2026.4.29 AND the QQBot admin command system is enabled with DM-only or allowFrom policies that can be bypassed.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data2026.4.29
Upgrade to OpenClaw version 2026.4.29 or later, which contains the fix for this policy bypass. Additionally, audit admin command routing logic to ensure policy checks cannot be bypassed through alternative contexts.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34507 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-34507 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data