---
id: GHSA-xr4f-mjxj-w6w5
title: 'OpenClaw: Non-owner chat senders could issue device-pairing bootstrap codes'
summary: 'OpenClaw: Non-owner chat senders could issue device-pairing bootstrap codes'
severity: high
cvss: 8.3
cwe:
  - CWE-863
vendor: openclaw
product: openclaw
ecosystem: npm
affected:
  - openclaw < 2026.5.4
patched:
  - openclaw 2026.5.4
published: '2026-07-02'
updated: '2026-07-02'
source: GHSA
sourceUrl: 'https://github.com/advisories/GHSA-xr4f-mjxj-w6w5'
references:
  - url: >-
      https://github.com/openclaw/openclaw/security/advisories/GHSA-xr4f-mjxj-w6w5
  - url: 'https://github.com/advisories/GHSA-xr4f-mjxj-w6w5'
tags:
  - ghsa
  - npm
ingestedAt: '2026-07-02T17:40:39.360Z'
---

## Overview

### Summary

The bundled device-pair plugin exposed `/pair` on normal chat command surfaces. In affected releases, authorized non-owner chat senders could issue device-pairing bootstrap codes without having owner, admin, or pairing scope.

This issue does not affect unauthenticated users. The caller must already be allowed to send commands to the agent through a configured chat channel.

### Affected configurations

This affects deployments where the bundled device-pair plugin is enabled and a non-owner sender is authorized to use normal chat commands, such as in a configured Telegram, Discord, or Slack agent.

### Impact

A non-owner authorized sender could create a setup code and use it before expiry to enroll a device with operator/node capabilities. That device would then retain persistent credentials until removed.

### Patched Versions

The first stable patched version is `2026.5.4`.

### Mitigations

Upgrade to `openclaw@2026.5.4` or later. Review paired devices and remove any unexpected entries. In shared chat channels, keep command access limited to users who should be allowed to manage device pairing.

## Affected packages

- `openclaw < 2026.5.4`

## Remediation

Upgrade to a patched release:

- `openclaw 2026.5.4`