CVE-2026-32067: Openclaw Authorization Bypass Vulnerability

CVE-2026-32067 Overview

CVE-2026-32067 is an authorization bypass vulnerability discovered in OpenClaw, a Node.js application. The vulnerability exists in the pairing-store access control mechanism for direct message pairing policy. This flaw allows attackers to reuse pairing approvals across multiple accounts, effectively bypassing authorization boundaries in multi-account deployments.

When an attacker is approved as a sender in one account, they can be automatically accepted in another account without explicit approval. This cross-account authorization bypass undermines the security model of the direct messaging system and could enable unauthorized communications.

Critical Impact
Attackers can bypass authorization boundaries in multi-account deployments by reusing pairing approvals, enabling unauthorized direct message access across different accounts.

Affected Products

OpenClaw versions prior to 2026.2.26
OpenClaw for Node.js (all platforms)
Multi-account OpenClaw deployments

Discovery Timeline

2026-03-21 - CVE-2026-32067 published to NVD
2026-03-24 - Last updated in NVD database

Technical Details for CVE-2026-32067

Vulnerability Analysis

This vulnerability (CWE-863: Incorrect Authorization) stems from improper authorization checks in OpenClaw's direct message pairing store. The pairing-store component is responsible for managing sender approvals in direct messaging workflows. However, the implementation fails to properly scope pairing approvals to individual accounts.

In multi-account deployment scenarios, when a user approves a sender for direct messaging in one account, that approval is inadvertently shared or accessible across other accounts. This means an attacker who gains sender approval in one context can leverage that same approval to bypass authorization checks in entirely separate account contexts.

The attack requires network access and some level of authenticated privileges (low), combined with active user interaction to initially approve the attacker as a sender. However, once this initial approval is obtained, the cross-account bypass requires no additional user action.

Root Cause

The root cause of CVE-2026-32067 is the failure to properly isolate pairing approvals within account-specific boundaries. The pairing-store access control mechanism does not adequately validate that a pairing approval is scoped to the specific account context in which it was granted. This allows approval tokens or state to be reused across account boundaries in multi-tenant or multi-account environments.

Attack Vector

The attack vector for this vulnerability involves the following sequence:

The attacker establishes a legitimate presence in the OpenClaw ecosystem and gains approval as a sender in one target account through normal direct messaging request flows
The attacker then targets a different account within the same multi-account deployment
Due to the authorization bypass, the pairing approval from the first account is recognized and accepted in the second account
The attacker gains unauthorized direct message access to the second account without explicit approval from that account's owner

This vulnerability is exploited over the network and requires the attacker to have low-level privileges (authenticated user status). The attack complexity is high as it requires specific multi-account deployment configurations and prior approval in at least one account.

Detection Methods for CVE-2026-32067

Indicators of Compromise

Unexpected direct message pairing approvals appearing in account logs without corresponding user actions
Sender approvals that span multiple accounts from the same origin identity
Authentication logs showing cross-account messaging patterns that bypass normal approval workflows
Anomalous pairing-store database entries with mismatched account identifiers

Detection Strategies

Implement logging and alerting for pairing approval events that reference accounts different from the current user context
Monitor for direct message sessions established without corresponding approval events in the target account
Audit pairing-store entries for cross-account references or approval reuse patterns
Deploy application-level monitoring to track authorization decisions in the DM subsystem

Monitoring Recommendations

Enable verbose logging for the pairing-store component to capture all authorization decisions
Configure alerts for any pairing operations that involve multiple distinct account contexts
Regularly audit direct message pairing relationships across all accounts in multi-account deployments
Monitor for unusual patterns in sender approval rates that may indicate exploitation attempts

How to Mitigate CVE-2026-32067

Immediate Actions Required

Upgrade OpenClaw to version 2026.2.26 or later immediately
Review all existing pairing approvals in multi-account deployments for unauthorized cross-account relationships
Temporarily disable multi-account direct messaging functionality if upgrade cannot be performed immediately
Audit logs for any evidence of cross-account authorization bypass exploitation

Patch Information

OpenClaw has released security patches to address this vulnerability. The fixes are available in the following commits:

For complete details on the vulnerability and remediation, refer to the GitHub Security Advisory GHSA-vjp8-wprm-2jw9.

Workarounds

Disable direct message pairing functionality in multi-account deployments until the patch can be applied
Implement network segmentation to isolate different account contexts
Deploy additional authorization checks at the application gateway level to validate account scope on pairing operations
Require manual re-approval of all senders after clearing existing pairing-store data

bash

# Upgrade OpenClaw to patched version
npm update openclaw@2026.2.26

# Verify installed version
npm list openclaw