openclaw
Affected
- introduced
0, fixed2026.3.13(semver)
Fixed versions
2026.3.13
Fix
- Fixed version
2026.3.13npm install [email protected]
Advisory
Also known as: CVE-2026-32987
OpenClaw bootstrap setup codes could be replayed to escalate pending pairing scopes before approval
Summaryopenclaw versions <= 2026.3.12 allowed bootstrap setup codes to be replayed before approval, which could widen the scopes on a pending device pairing request.
Affected Packages / Versions
openclaw (npm)<= 2026.3.122026.3.13Details
The vulnerable path was bootstrap token verification in src/infra/device-bootstrap.ts. In affected releases, a valid bootstrap setup code could be verified more than once before the pairing request was approved. That allowed a second verification attempt to mutate a pending device pairing and request broader scopes, including escalation from a lower operator scope to operator.admin, before an approver finalized the pairing.
This issue is in scope under OpenClaw's trust model because bootstrap setup codes are an authentication primitive for device pairing and the replay changed the privileges granted to the pending device.
Fix[email protected] makes bootstrap setup codes single-use. Current code consumes the bootstrap token record on the first successful verification, so replay attempts fail before pending scopes can be widened.
Regression coverage exists in src/infra/device-pairing.test.ts (rejects bootstrap token replay before pending scope escalation can be approved).
Fix Commit(s)
1803d16d5cec970c54b0e1ac46b31b1cbade335cThanks @tdjackey for reporting.
High Basis: The source's own band: HIGH
0, fixed 2026.3.13 (semver)2026.3.13
2026.3.13npm 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