Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.6amended

OpenClaw bootstrap setup codes could be replayed to escalate pending pairing scopes before approval

CVE-2026-32987GHSA-63f5-hhc7-cx6p

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (openclaw 2026.3.13), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm openclaw

    Affected
    <= 2026.3.12
    Fixed in
    2026.3.13

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
8.6 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-32987: 0.36% estimated exploitation activity in the next 30 days; percentile 29.52 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary openclaw 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 - Package: openclaw (npm) - Affected versions: <= 2026.3.12 - Fixed version: 2026.3.13 Details 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 openclaw@2026.3.13 makes bootstrap setup codes single-use. Current code…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-63f5-hhc7-cx6p

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-63f5-hhc7-cx6p

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-32987

Advisory: OpenClaw bootstrap setup codes could be replayed to escalate pending pairing scopes before approval
IDs: CVE-2026-32987, GHSA-63f5-hhc7-cx6p
Record: https://patchnext.com/advisories/cve-2026-32987 (revision 3, source checked 26 Oct 2026, 12:46 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: openclaw 2026.3.13. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm openclaw: affected <= 2026.3.12; fixed in 2026.3.13

## Suggested inspection (read-only)
- `npm ls openclaw --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on openclaw.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-63f5-hhc7-cx6p (OSV record GHSA-63f5-hhc7-cx6p lists affected ranges: npm openclaw >=0 <2026.3.13 (fixed))
- Verified: https://github.com/advisories/GHSA-63f5-hhc7-cx6p (GitHub-reviewed advisory GHSA-63f5-hhc7-cx6p lists affected ranges: npm openclaw >=0 <=2026.3.12)

Commands are suggestions: review each one before running it.

Loading voting…