CVE-2026-53815: OpenClaw Message Read Actions Bypass Channel Allowlist Checks

openclaw Updated 02 Jul 2026

Summary

02/07/2026
Yes i
High
6.5

CVE-2026-53815: OpenClaw: Message read actions could skip channel allowlist checks. Affects openclaw versions < 2026.5.19. Fixed in 2026.5.19. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

OpenClaw is an open-source messaging framework designed to facilitate secure communication between various applications. It allows developers to implement message delivery systems with a focus on trust and security. However, certain configurations of OpenClaw can expose it to vulnerabilities, particularly concerning message read actions that may bypass essential security checks.

Vulnerability Detail

The vulnerability identified as CVE-2026-53815 arises from the failure of message read actions to enforce channel allowlist checks. This flaw allows lower-trust callers to access messages from channels that they should not have permission to read. The implications of this vulnerability can lead to unauthorized access to sensitive information, depending on the operator's configuration and the extent to which lower-trust inputs can reach the affected message read action.

How To Fix

Latest published version: 2026.10.6 as of 22 Oct 2026

npm install openclaw@2026.10.6

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2026.5.19

This is the first release that contains the fix.

npm install openclaw@2026.5.19

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a temporary workaround, limit message read actions to trusted operators and maintain narrow channel allowlists. Additionally, avoid sharing a single Gateway between users of differing trust levels, and disable the affected feature when it is not necessary.

Conclusion

CVE-2026-53815 presents a significant security risk for OpenClaw users, allowing unauthorized access to messages. It is crucial to update to the patched version 2026.5.19 and implement recommended workarounds to mitigate potential risks. Regular monitoring with tools like Vulert can help maintain security.

See every vulnerability recorded for openclaw →

Share this vulnerability

FAQ

CVE-2026-53815 is a vulnerability in OpenClaw that allows unauthorized message access due to bypassed channel allowlist checks.

You can check if your application is affected by using Vulert, which monitors vulnerabilities in your package-lock.json file. Visit Vulert Scanner for a quick assessment without signup.

The vulnerability can lead to unauthorized access to messages from channels that should be restricted, potentially exposing sensitive information.

If immediate updates are not possible, implement the suggested workarounds to limit access and mitigate risks until you can upgrade.

While the primary risk is unauthorized access, it is crucial to assess your application's configuration to determine if sensitive data could be exposed.

Related vulnerabilities

Recent vulnerabilities recorded for openclaw.

How To Fix

Latest published version: 2026.10.6 as of 22 Oct 2026

npm install openclaw@2026.10.6

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2026.5.19

This is the first release that contains the fix.

npm install openclaw@2026.5.19

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback