openclaw
Affected
- introduced
0, fixed2026.2.26(semver)
Fixed versions
2026.2.26
Fix
- Fixed version
2026.2.26npm install [email protected]
Advisory
Also known as: CVE-2026-32067
OpenClaw has cross-account DM pairing authorization bypass via unscoped pairing store access
Summary
OpenClaw had account-scope gaps in pairing-store access for DM pairing policy, which could let a pairing approval from one account authorize the same sender on another account in multi-account setups.
Impact
This is an authorization-boundary weakness in multi-account channel deployments. A sender approved in one account could be accepted in another account before explicit approval there.
Affected Packages / Versions
openclaw (npm)2026.2.25<= 2026.2.25>= 2026.2.26Fix
OpenClaw now enforces account-scoped pairing reads/writes consistently across core and extension message channels, with stricter runtime/SDK helpers and shared policy wiring to prevent cross-account pairing bleed.
Fix Commit(s)
a0c5e28f3bf0cc0cd9311f9e9ec2ca0352550dcfbce643a0bd145d3e9cb55400af33bd1b85baeb02Release Process Notepatched_versions is pre-set to the planned next release (2026.2.26). After npm publish of that version, this advisory is ready to publish without further content edits.
OpenClaw thanks @tdjackey for reporting.
Low Basis: The source's own band: LOW
0, fixed 2026.2.26 (semver)2026.2.26
2026.2.26npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0