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.
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.
openclaw (npm)2026.2.25<= 2026.2.25>= 2026.2.26OpenClaw 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.
a0c5e28f3bf0cc0cd9311f9e9ec2ca0352550dcfbce643a0bd145d3e9cb55400af33bd1b85baeb02patched_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.
{
"nvd_published_at": null,
"github_reviewed_at": "2026-03-04T18:56:10Z",
"cwe_ids": [
"CWE-863"
],
"severity": "LOW",
"github_reviewed": true
}