Is there a public PoC exploit available for CVE-2026-32067?

Yes, a public proof-of-concept exploit is available for CVE-2026-32067. Prioritise patching immediately. EPSS: 0.0%.

How to fix or mitigate CVE-2026-32067?

During next maintenance window: Apply vendor patches when convenient. Vendor patch is available.

Openclaw CVE-2026-32067

Q: What is the CVSS score of CVE-2026-32067?

CVE-2026-32067 has a CVSS 4.0 base score of 2.0 (Low). CVSS vector: CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:A/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.0%.

Q: Which versions of Openclaw are affected by CVE-2026-32067?

CVE-2026-32067 is a low-severity vulnerability in OpenClaw versions prior to 2026.2.26 (CVSS 3.7).. A patch is available.

EUVD-2026-13968 LOW

Incorrect Authorization (CWE-863)

2026-03-21 VulnCheck

GHSA-vmvw-pwwf-cc2w

Authentication Bypass Openclaw

2.0

CVSS 4.0 · NVD

Severity by source

NVD PRIMARY

2.0 LOW

CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:A/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

High

Privileges Required

Low

User Interaction

Scope

Lifecycle Timeline

CVSS changed

May 26, 2026 - 14:22 NVD

3.7 (LOW) 2.0 (LOW)

PoC Detected

Mar 24, 2026 - 21:09 vuln.today

Public exploit code

EUVD ID Assigned

Mar 21, 2026 - 01:00 euvd

EUVD-2026-13968

Analysis Generated

Mar 21, 2026 - 01:00 vuln.today

Patch released

Mar 21, 2026 - 01:00 nvd

Patch available

CVE Published

Mar 21, 2026 - 00:42 nvd

LOW 3.7

Blast Radius

ecosystem impact

† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth

2 npm packages depend on openclaw (2 direct, 0 indirect)

Ecosystem-wide dependent count for version 2026.2.26.

DescriptionCVE.org

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.

AnalysisAI

OpenClaw versions prior to 2026.2.26 contain an authorization bypass vulnerability in the pairing-store access control mechanism for direct message pairing policies, allowing attackers to reuse pairing approvals across multiple accounts in multi-account deployments. An authenticated attacker (PR:L) who has been approved as a sender in one account can be automatically accepted in another account without explicit re-approval, effectively bypassing authorization boundaries between accounts. The vulnerability has a CVSS score of 3.7 with medium attack complexity and low confidentiality and integrity impacts; no active exploitation in the wild (KEV) or public proof-of-concept has been confirmed, but patches are available from the vendor.

Technical ContextAI

OpenClaw (cpe:2.3:a:openclaw:openclaw:*:*:*:*:*:*:*:*) implements a pairing-store access control mechanism to manage direct message (DM) pairing policies in multi-account environments. This mechanism is intended to enforce per-account authorization boundaries, requiring explicit approval for each account-sender pairing. The vulnerability stems from a flaw in CWE-863 (Incorrect Authorization), where the access control logic fails to properly validate and isolate pairing approval state between different user accounts. Rather than enforcing account-scoped approval checks, the system permits pairing approvals obtained in one account context to be reused or carried over into other account contexts, creating a cross-account privilege escalation path. This is particularly dangerous in multi-tenant or multi-account deployments where strict authorization boundaries are critical.

RemediationAI

Upgrade OpenClaw to version 2026.2.26 or later as released by the vendor; refer to the GitHub security advisory at https://github.com/openclaw/openclaw/security/advisories/GHSA-vjp8-wprm-2jw9 for specific patch details and release notes. If immediate upgrade is not feasible, implement compensating controls by restricting direct message pairing workflows to single-account contexts or by enforcing explicit per-account re-approval policies at the application configuration level, disabling automatic pairing reuse across account boundaries. Additionally, audit existing pairing approvals across all accounts for unauthorized cross-account pairings and revoke any suspicious sender approvals that may have been propagated without explicit consent. Network segmentation and role-based access controls limiting who can perform pairing operations will further reduce the attack surface.