openclaw
Affected
- introduced
2026.2.26, fixed2026.3.31(semver)
Fixed versions
2026.3.31
Fix
- Fixed version
2026.3.31npm install [email protected]
Advisory
Also known as: CVE-2026-41346
OpenClaw: Pairing pending-request caps were enforced per channel instead of per account
Summary
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.
Impact
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.
Affected Packages / Versions
openclaw (npm)>= 2026.2.26, < 2026.3.31>= 2026.3.312026.4.1Fix Commit(s)
9bc1f896c8cd325dd4761681e9bdb8c425f69785 — scope pending request caps per accountRelease Process Note
The 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.
Medium Basis: The source's own band: MODERATE
2026.2.26, fixed 2026.3.31 (semver)2026.3.31
2026.3.31npm 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