GHSA-xr4f-mjxj-w6w5
Suggest an improvement- Source
- https://github.com/advisories/GHSA-xr4f-mjxj-w6w5
- Import Source
- https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/07/GHSA-xr4f-mjxj-w6w5/GHSA-xr4f-mjxj-w6w5.json
- JSON Data
- https://api.osv.dev/v1/vulns/GHSA-xr4f-mjxj-w6w5
- Aliases
- Downstream
- Published
- 2026-07-02T16:55:09Z
- Modified
- 2026-07-08T07:35:36Z
- Severity
-
- 8.3 (High) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L CVSS Calculator
- Summary
- OpenClaw: Non-owner chat senders could issue device-pairing bootstrap codes
- Details
-
Summary
The bundled device-pair plugin exposed
/pairon 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.4or 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. - Database specific
{ "cwe_ids": [ "CWE-863" ], "github_reviewed": true, "github_reviewed_at": "2026-07-02T16:55:09Z", "nvd_published_at": null, "severity": "HIGH" }- References
Affected packages
npm / openclaw
Package
- Name
- openclaw
- View open source insights on deps.dev
- Purl
- pkg:npm/openclaw