Before OpenClaw 2026.3.31, pending pairing-request caps were enforced per channel file instead of per account. On multi-account channel setups, requests from other accounts could fill the shared pending window and block new pairing challenges on an unaffected account.
This issue could deny new pairing or onboarding on another account until an existing request was approved or expired. It was an availability-only bug; it did not allow cross-account approval, data access, or authorization bypass.
openclaw (npm)>= 2026.2.26, < 2026.3.31>= 2026.3.312026.4.19bc1f896c8cd325dd4761681e9bdb8c425f69785 — scope pending request caps per accountThe fix shipped in OpenClaw 2026.3.31 on March 31, 2026. The current published npm release 2026.4.1 from April 1, 2026 also contains the fix.
Thanks @smaeljaish771 for reporting.
{
"cwe_ids": [],
"github_reviewed_at": "2026-04-07T18:14:44Z",
"nvd_published_at": null,
"severity": "MODERATE",
"github_reviewed": true
}