CVE-2026-32067

Published: Mar 21, 2026 Last Modified: Mar 21, 2026
ExploitDB:
Other exploit source:
Google Dorks:
LOW 2,0
Attack Vector: network
Attack Complexity: high
Privileges Required: low
User Interaction: active
Confidentiality: N/A
Integrity: N/A
Availability: N/A
LOW 3,7
Attack Vector: network
Attack Complexity: high
Privileges Required: low
User Interaction: required
Scope: unchanged
Confidentiality: low
Integrity: low
Availability: none

Description

AI Translation Available

OpenClaw versions prior to 2026.2.26 contains an authorization bypass vulnerability in the pairing-store access control for direct message pairing policy that allows attackers to reuse pairing approvals across multiple accounts. An attacker approved as a sender in one account can be automatically accepted in another account in multi-account deployments without explicit approval, bypassing authorization boundaries.

863

Incorrect Authorization

Incomplete
Common Consequences
Security Scopes Affected:
Confidentiality Integrity Access Control Availability
Potential Impacts:
Read Application Data Read Files Or Directories Modify Application Data Modify Files Or Directories Gain Privileges Or Assume Identity Bypass Protection Mechanism Execute Unauthorized Code Or Commands Dos: Crash, Exit, Or Restart Dos: Resource Consumption (Cpu) Dos: Resource Consumption (Memory) Dos: Resource Consumption (Other)
Applicable Platforms
Technologies: Database Server, Not Technology-Specific, Web Server
View CWE Details
https://github.com/openclaw/openclaw/commit/a0c5e28f3bf0cc0cd9311f9e9ec2ca03525…
https://github.com/openclaw/openclaw/commit/bce643a0bd145d3e9cb55400af33bd1b85b…
https://github.com/openclaw/openclaw/security/advisories/GHSA-vjp8-wprm-2jw9
https://www.vulncheck.com/advisories/openclaw-cross-account-authorization-bypas…