dbcve.org
OpenclawApplication

CVE-2026-53815

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-11
Fix available
A fix is available. Upgrade to 2026.5.19 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
OpenClaw before 2026.5.19 contains an authorization bypass vulnerability in message read actions that skips channel allowlist checks. Lower-trust callers can request messages from channels not intended for them by exploiting insufficient validation in the affected feature, potentially exposing sensitive channel messages.

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 confidence

OpenClaw before version 2026.5.19 has an authorization bypass vulnerability in its message read functionality. The application fails to properly validate channel allowlist permissions when processing message read requests, allowing lower-privileged users to access messages from channels outside their authorized scope.

MitigationUpgrade to OpenClaw version 2026.5.19 or later. Additionally, implement explicit channel allowlist validation checks in all message read operations to ensure users can only access channels explicitly permitted for their trust level.

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
OpenclawApplication
Affected:< 2026.5.19

CVSS 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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify OpenClaw installation and version
    Locate the OpenClaw application installation and determine its installed version number. Common methods include: checking the application executable metadata, reviewing version files in the installation directory, or running 'openclaw --version' if a CLI is available.
    Affected if The installed version is lower than 2026.5.19
  2. Verify message read functionality is present
    Confirm that the OpenClaw message reading feature is enabled and accessible in the environment. Check application modules or feature flags related to message handling.
    Affected if Message read functionality exists and is accessible to users in the application
  3. Examine channel allowlist configuration
    Review the OpenClaw configuration files or database entries that define channel access permissions. Look for settings that control which channels users at different trust levels can access.
    Affected if Channel allowlist permissions are defined but may not be properly enforced in message read operations
  4. Review user privilege assignments and channel access mapping
    Inspect the user role definitions and their associated channel access permissions. Identify any users with lower trust levels assigned to specific channel scopes.
    Affected if Users with lower privilege levels exist and have defined channel access restrictions

A user is affected if OpenClaw version is below 2026.5.19 AND the message read functionality is accessible to users with lower privilege levels who should be restricted to specific channel allowlists.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2026.5.19 or later
Fixed in 2026.5.19
Interim mitigation

Upgrade to OpenClaw version 2026.5.19 or later. Additionally, implement explicit channel allowlist validation checks in all message read operations to ensure users can only access channels explicitly permitted for their trust level.

Recommended fix Moderate confidence

2026.5.19

  1. 1. Back up your current Openclaw installation and any associated databases
  2. 2. Review the release notes for version 2026.5.19 to understand changes
  3. 3. Download Openclaw version 2026.5.19 or later from the official repository
  4. 4. Stop the currently running Openclaw service
  5. 5. Install the upgraded version following standard installation procedures
  6. 6. Verify that the message read action now properly enforces channel allowlist checks
  7. 7. Test that users can only access channels they are authorized to view
  8. 8. Restart the Openclaw service

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Openclaw Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-53815 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-53815 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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