Authorization Bypass Vulnerability in OpenClaw: Feishu Allowlist Collision

openclaw Updated 04 Mar 2026

Summary

03/03/2026

Disclosed on

MODERATE

Severity

Yes i

Fix available

Moderate

Severity

5.3

CVSS Score

GHSA-j4xf-96qf-rx69: OpenClaw has a Feishu allowFrom authorization bypass via display-name collision. Affects openclaw versions < 2026.2.22. Fixed in 2026.2.22. 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 an open-source package designed for integrating various communication channels, including Feishu. It utilizes an ID-based allowlist for authorization, ensuring that only specified users can send messages through the platform. However, a flaw in its implementation allows for potential bypass of this security feature, exposing deployments to unauthorized access.

Vulnerability Detail

The vulnerability arises from the channels.feishu.allowFrom feature, which is intended to restrict access based on a list of allowed IDs. However, the implementation incorrectly allows mutable sender display names to match with allowlisted IDs, leading to a scenario where an attacker can set their display name to match an allowlisted ID. This results in unauthorized users being able to send messages, as the system fails to enforce strict ID-only matching, thereby compromising the integrity of the authorization process.

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.2.22

This is the first release that contains the fix.

npm install openclaw@2026.2.22

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 it becomes available.

Conclusion

The OpenClaw package has a significant vulnerability that allows for authorization bypass through display-name collisions in Feishu allowlist checks. It is essential for users to update to the patched version 2026.2.22 to secure their deployments and prevent unauthorized access.

See every vulnerability recorded for openclaw →