https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 30 Sep 2026 21:38:08 +0000 https://vulnerability.circl.lu/vuln/cve-2026-32905 <p><strong>Affected:</strong> OpenClaw</p> <p>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.</p> <p><strong>Affected:</strong> OpenClaw</p> <p>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.</p> https://vulnerability.circl.lu/vuln/cve-2026-32905 https://vulnerability.circl.lu/vuln/ghsa-xr4f-mjxj-w6w5 <p><strong>Affected:</strong> npm: openclaw</p> <p>### Summary</p> <p>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.</p> <p>This issue does not affect unauthenticated users. The caller must already be allowed to send commands to the agent through a configured chat channel.</p> <p>### Affected configurations</p> <p>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.</p> <p>### Impact</p> <p>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.</p> <p>### Patched Versions</p> <p>The first stable patched version is `2026.5.4`.</p> <p>### Mitigations</p> <p>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.</p> <p><strong>Affected:</strong> npm: openclaw</p> <p>### Summary</p> <p>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.</p> <p>This issue does not affect unauthenticated users. The caller must already be allowed to send commands to the agent through a configured chat channel.</p> <p>### Affected configurations</p> <p>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.</p> <p>### Impact</p> <p>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.</p> <p>### Patched Versions</p> <p>The first stable patched version is `2026.5.4`.</p> <p>### Mitigations</p> <p>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.</p> https://vulnerability.circl.lu/vuln/ghsa-xr4f-mjxj-w6w5