OpenClaw up to 2026.2.21 Display Name authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.1 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in OpenClaw up to 2026.2.21. This affects an unknown part of the component Display Name Handler. Performing a manipulation results in authorization. This vulnerability is cataloged as CVE-2026-32021. It is possible to initiate the attack remotely. There is no exploit available. You should upgrade the affected component.
Details
A vulnerability was found in OpenClaw up to 2026.2.21. It has been classified as problematic. This affects some unknown functionality of the component Display Name Handler. The manipulation with an unknown input leads to a authorization vulnerability. CWE is classifying the issue as CWE-863. The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
OpenClaw versions prior to 2026.2.22 contain an authorization bypass vulnerability in the Feishu allowFrom allowlist implementation that accepts mutable sender display names instead of enforcing ID-only matching. An attacker can set a display name equal to an allowlisted ID string to bypass authorization checks and gain unauthorized access.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-32021 since 03/10/2026. The exploitability is told to be difficult. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available.
Upgrading to version 2026.2.22 eliminates this vulnerability. Applying the patch 4ed87a667263ed2d422b9d5d5a5d326e099f92c7 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2026-0586). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Affected
- Open Source OpenClaw
Product
Type
Name
Version
- 2026.2.0
- 2026.2.1
- 2026.2.2
- 2026.2.3
- 2026.2.4
- 2026.2.5
- 2026.2.6
- 2026.2.7
- 2026.2.8
- 2026.2.9
- 2026.2.10
- 2026.2.11
- 2026.2.12
- 2026.2.13
- 2026.2.14
- 2026.2.15
- 2026.2.16
- 2026.2.17
- 2026.2.18
- 2026.2.19
- 2026.2.20
- 2026.2.21
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 6.2VulDB Meta Temp Score: 6.1
VulDB Base Score: 5.6
VulDB Temp Score: 5.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 6.5
NVD Vector: 🔒
CNA Base Score: 6.5
CNA Vector (VulnCheck): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: AuthorizationCWE: CWE-863 / CWE-285 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: OpenClaw 2026.2.22
Patch: 4ed87a667263ed2d422b9d5d5a5d326e099f92c7
Timeline
03/10/2026 CVE reserved03/20/2026 Advisory disclosed
03/20/2026 VulDB entry created
03/26/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-j4xf-96qf-rx69
Status: Confirmed
CVE: CVE-2026-32021 (🔒)
GCVE (CVE): GCVE-0-2026-32021
GCVE (VulDB): GCVE-100-351969
CERT Bund: WID-SEC-2026-0586 - OpenClaw: Mehrere Schwachstellen
Entry
Created: 03/20/2026 08:31Updated: 03/26/2026 08:15
Changes: 03/20/2026 08:31 (78), 03/23/2026 12:50 (7), 03/25/2026 02:04 (12), 03/26/2026 08:15 (4)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.