Cross-account authorization bypass via unscoped pairing store
Published Mar 21, 2026 · Updated Mar 21, 2026
Incorrect authorization in OpenClaw before 2026.2.26 allows remote authenticated users to reuse DM pairing approval across accounts. Pairing-store readers and writers keyed approvals by channel without consistently supplying an account ID, so an allowlist entry from one account was read by another. Exploitation requires a multi-account channel deployment, an approval in one account, and interaction on another; it grants unintended message access without affecting availability.
Summary
What happened
Incorrect authorization in OpenClaw before 2026.2.26 allows remote authenticated users to reuse DM pairing approval across accounts. Pairing-store readers and writers keyed approvals by channel without consistently supplying an account ID, so an allowlist entry from one account was read by another. Exploitation requires a multi-account channel deployment, an approval in one account, and interaction on another; it grants unintended message access without affecting availability.
The record
- CVE
- CVE-2026-32067
- Published
- Mar 21, 2026
- Updated
- Mar 21, 2026
- Vendor
- OpenClaw Foundation
- Product
- OpenClaw
- Classifications
- CWE-863, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 21, 2026CVE publishedPublication date reported by the CVE source.
- Mar 21, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2026.2.26
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo