Cross-Channel Allowlist Write Vulnerability in OpenClaw Package

openclaw Updated 09 Apr 2026

Summary

09/04/2026

Disclosed on

MODERATE

Severity

Yes i

Fix available

Moderate

Severity

4.8

CVSS Score

GHSA-vc32-h5mq-453v: OpenClaw: /allowlist omits owner-only enforcement for cross-channel allowlist writes. Affects openclaw versions < 2026.4.8. Fixed in 2026.4.8. 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 Browse

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.

Background

OpenClaw is a user-controlled local assistant designed to facilitate various tasks for users. It allows for the management of allowlists, which are essential for controlling access to different functionalities within the application. However, a significant vulnerability has been identified that affects the integrity of these allowlists, particularly in scenarios involving cross-channel interactions.

Vulnerability Detail

The vulnerability arises from the /allowlist endpoint, which fails to enforce owner-only restrictions for allowlist writes across different channels. This means that an authorized non-owner sender can exploit this weakness to perform unauthorized allowlist modifications on channels they do not own. The implications of this vulnerability are serious, as it can lead to unauthorized access and manipulation of functionalities intended for specific users, thereby compromising the security model of 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.4.8

This is the first release that contains the fix.

npm install openclaw@2026.4.8

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

Workaround

Currently, there are no specific workarounds mentioned for this vulnerability. The best course of action is to apply the patch as soon as possible to mitigate any potential risks.

Conclusion

The OpenClaw package has a vulnerability that allows unauthorized allowlist writes across channels, posing a risk to user security. It is crucial to update to the patched version 2026.4.8 to mitigate this risk. Regular monitoring and updates are essential for maintaining application security.

See every vulnerability recorded for openclaw →