OpenClaw before 2026.3.13 allows bootstrap setup codes to be replayed during device pairing verification in src/infra/device-bootstrap.ts. Attackers can verify a valid bootstrap code multiple times before approval to escalate pending pairing scopes, including privilege escalation to operator.admin.
Security readout for executives and security teams
Plain-English summary
OpenClaw versions before 2026.3.13 can let a bootstrap setup code be reused during device pairing. A valid code could be verified more than once before approval, allowing a pending pairing request to gain broader permissions, including operator.admin. This is critical because it affects initial trust establishment for devices.
Executive priority
Treat this as urgent for any OpenClaw environment using device pairing. Prioritize upgrade and review of pending pairings because the issue targets a trust-onboarding path and can grant administrative operator privileges without prior authentication.
Technical view
The issue is a CWE-294 authentication bypass by capture-replay in src/infra/device-bootstrap.ts. During pairing verification, bootstrap setup codes were replayable before approval, enabling escalation of pending pairing scopes. The bundled CVSS v3.1 score is 9.8 with network attack vector, no privileges, and no user interaction.
Likely exposure
Exposure is likely limited to OpenClaw deployments running versions before 2026.3.13 that use device bootstrap pairing. Systems not using OpenClaw or already on 2026.3.13 or later are not indicated as affected in the supplied sources.
Exploitation context
The source bundle does not state active exploitation, and KEV is false. The risk is still high because the flaw is network-accessible, low-complexity, unauthenticated, and can lead to operator.admin scope escalation during device pairing.
Researcher notes
Evidence identifies replayable bootstrap setup codes in device pairing verification, with privilege escalation to operator.admin. Public sources in the bundle identify the vulnerable component and fixed release, but do not provide evidence of in-the-wild exploitation or additional mitigations beyond vendor guidance and patching.
Mitigation direction
Upgrade OpenClaw to 2026.3.13 or later.
Review the GitHub advisory and patch commit for vendor-specific remediation details.
Rotate or invalidate outstanding bootstrap setup codes after upgrading.
Review pending device pairings and remove unexpected operator.admin scopes.
Monitor vendor guidance for any additional hardening instructions.
Validation and detection
Inventory OpenClaw deployments and confirm versions are at least 2026.3.13.
Identify whether device bootstrap pairing is enabled in each deployment.
Review pairing logs for repeated verification of the same bootstrap code.
Check pending pairings for unexpected scope escalation before approval.
Confirm the patched code prevents bootstrap code replay during verification.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-294: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
3Timeline events
1ADP providers
4Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-294 · source CWE mapping
Authentication Bypass by Capture-replay
Authentication Bypass by Capture-replay represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.