Summary
OpenClaw: Paired-device pairing actions were not limited to the caller device
Affected Packages / Versions
- Package:
openclaw(npm) - Affected versions:
< 2026.4.20 - Patched version:
2026.4.20
Release
Fixed in OpenClaw 2026.4.20.
Impact
A paired device session with limited pairing scope could enumerate global pairing state and act on pairing requests that belonged to another device within the same gateway scope ceiling.
This is a same-gateway paired-device authorization bug, not a remote unauthenticated issue. Severity is low.
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.
Affected versions
Security releases
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. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Pairing management actions are now limited to the caller device, so non-admin paired-device sessions cannot approve or operate on unrelated pending device requests.
Fix commit:
5a12f30441d5b0b151f550daa2c5c9e8db61e2e6
Frequently Asked Questions
- What is GHSA-XRQ9-JM7V-G9H7? GHSA-XRQ9-JM7V-G9H7 is a low-severity incorrect authorization vulnerability in openclaw (npm), affecting versions < 2026.4.20. It is fixed in 2026.4.20. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
- Which versions of openclaw are affected by GHSA-XRQ9-JM7V-G9H7? openclaw (npm) versions < 2026.4.20 is affected.
- Is there a fix for GHSA-XRQ9-JM7V-G9H7? Yes. GHSA-XRQ9-JM7V-G9H7 is fixed in 2026.4.20. Upgrade to this version or later.
- Is GHSA-XRQ9-JM7V-G9H7 exploitable, and should I be worried? Whether GHSA-XRQ9-JM7V-G9H7 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-XRQ9-JM7V-G9H7 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-XRQ9-JM7V-G9H7? Upgrade
openclawto 2026.4.20 or later.