https://vulnerability.circl.lu/rss/recent/all/10 Most recent entries from all 2026-09-30T21:38:08.728889+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent entries. https://vulnerability.circl.lu/vuln/cve-2026-32905 CVE-2026-32905 — OpenClaw < 2026.5.4 - Unauthorized Device-Pairing Bootstrap Code Issuance via Chat Command 2026-09-30T21:38:08.730344+00:00

Affected: OpenClaw

OpenClaw before 2026.5.4 contains an authorization bypass vulnerability in the bundled device-pair plugin that allows non-owner authorized chat senders to issue device-pairing bootstrap codes without proper scope validation. Attackers with chat command access can create setup codes to enroll devices with operator/node capabilities, granting persistent credentials until manual removal.

 https://vulnerability.circl.lu/vuln/ghsa-xr4f-mjxj-w6w5 GHSA-xr4f-mjxj-w6w5 — OpenClaw: Non-owner chat senders could issue device-pairing bootstrap codes 2026-09-30T21:38:08.730417+00:00

Affected: npm: openclaw

### 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.