openclaw

GHSA-XR4F-MJXJ-W6W5

GHSA-XR4F-MJXJ-W6W5 is a high-severity incorrect authorization vulnerability in openclaw (npm), affecting versions < 2026.5.4. It is fixed in 2026.5.4.

Key facts
CVSS score
8.3
High
Attack vector
Network
Issuing authority
GitHub Advisory Database
Affected package
openclaw
Fixed in
2026.5.4
Disclosed
Not available

Summary

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 [email protected] 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.

Impact

What is incorrect authorization?

The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.

Severity and exposure

GHSA-XR4F-MJXJ-W6W5 has a CVSS score of 8.3 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.

A fixed version is available (2026.5.4). Upgrading removes the vulnerable code path.

Affected versions

npm

  • openclaw (< 2026.5.4)

Security releases

  • openclaw → 2026.5.4 (npm)
Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.

Kodem's runtime-powered SCA identifies whether GHSA-XR4F-MJXJ-W6W5 is reachable in your applications. Explore open-source security for your team.

See if GHSA-XR4F-MJXJ-W6W5 is reachable in your applications. Get a demo

Already deployed Kodem? See GHSA-XR4F-MJXJ-W6W5 in your environment

Remediation advice

Upgrade openclaw to 2026.5.4 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently asked questions about GHSA-XR4F-MJXJ-W6W5

What is GHSA-XR4F-MJXJ-W6W5?

GHSA-XR4F-MJXJ-W6W5 is a high-severity incorrect authorization vulnerability in openclaw (npm), affecting versions < 2026.5.4. It is fixed in 2026.5.4. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.

How severe is GHSA-XR4F-MJXJ-W6W5?

GHSA-XR4F-MJXJ-W6W5 has a CVSS score of 8.3 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of openclaw are affected by GHSA-XR4F-MJXJ-W6W5?

openclaw (npm) versions < 2026.5.4 is affected.

Is there a fix for GHSA-XR4F-MJXJ-W6W5?

Yes. GHSA-XR4F-MJXJ-W6W5 is fixed in 2026.5.4. Upgrade to this version or later.

Is GHSA-XR4F-MJXJ-W6W5 exploitable, and should I be worried?

Whether GHSA-XR4F-MJXJ-W6W5 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo

What actually determines whether GHSA-XR4F-MJXJ-W6W5 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix GHSA-XR4F-MJXJ-W6W5?

Upgrade openclaw to 2026.5.4 or later.

Stop the waste.
Protect your environment with Kodem.