CVE-2026-32027
Authorization Bypass in OpenClaw DM Pairing Enables Group Message Access
Publication date: 2026-03-19
Last updated on: 2026-03-26
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| openclaw | openclaw | to 2026.2.26 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-22 | The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. |
| 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in OpenClaw versions prior to 2026.2.26 and involves an authorization bypass. Specifically, identities paired via direct messaging (DM pairing-store identities) are incorrectly considered eligible for group allowlist authorization checks. Attackers can exploit this flaw by using a sender approved through DM pairing to bypass group message access controls, even if the sender is not explicitly listed in the groupAllowFrom list.
How can this vulnerability impact me? :
The impact of this vulnerability is that unauthorized users can gain access to group messages by bypassing group sender allowlist checks. This means attackers can read or potentially interact with group messages without proper authorization, leading to a breach of confidentiality.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know