CVE-2026-53833
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 an authorization bypass vulnerability in the QQBot streaming command that allows authenticated senders to mutate configuration without explicit allowFrom restrictions. Attackers can modify QQBot streaming configuration outside intended admin policy by reaching the affected command without non-wildcard allowlist entry requirements.
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 before version 2026.4.29 contains an authorization bypass in the QQBot streaming command that allows authenticated users to modify streaming configuration without requiring explicit allowFrom restrictions. The vulnerability exploits the lack of non-wildcard allowlist entry requirements, enabling attackers to bypass intended admin policy and mutate settings outside their authorized scope.
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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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.
-
Determine installed OpenClaw versionRun the version command for OpenClaw (typically 'openclaw --version' or check the package manifest) to identify the exact version numberAffected if The installed version is lower than 2026.4.29
-
Verify QQBot streaming feature is enabledCheck the OpenClaw configuration files or running service for the QQBot module and streaming command being activeAffected if The QQBot streaming command is enabled and accessible to authenticated users
-
Inspect allowFrom restrictions on streaming commandReview the OpenClaw access control configuration for the streaming command, specifically looking for allowFrom entries and whether wildcard policies are being enforcedAffected if The allowFrom restrictions are not properly enforcing non-wildcard allowlist entries, allowing authenticated senders to bypass admin-only policies
-
Confirm authenticated user access to streaming commandTest or audit whether non-admin authenticated users can reach the streaming configuration mutation endpointAffected if Authenticated users without explicit allowFrom entries can modify streaming configuration
You are affected if your OpenClaw version is below 2026.4.29 AND the QQBot streaming command is enabled with improperly configured allowFrom restrictions that allow authenticated bypass.
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.
dbcve · scoped2026.4.29
Upgrade to OpenClaw 2026.4.29 or later, and ensure explicit non-wildcard allowlist entries are configured for the QQBot streaming command to enforce proper authorization boundaries.
2026.4.29
- Upgrade OpenClaw to version 2026.4.29 or later to remediate the authorization bypass vulnerability in the QQBot streaming command
- After upgrading, verify that allowFrom restrictions are properly enforced for the QQBot streaming configuration
- Review existing QQBot streaming configuration to ensure no unauthorized modifications were made during the vulnerable period
- Confirm that the allowFrom policy now requires non-wildcard entries for proper authorization
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-53833 — 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-53833 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