Summary
OpenClaw: Node exec approvals could be replayed across nodes
exec.approval requests for host=node were not explicitly bound to the target nodeId, so an approval intended for one node could be replayed for a different node under the same operator-controlled gateway fleet.
Affected Packages / Versions
- Package:
openclaw(npm) - Affected:
<= 2026.2.22-2 - Fixed:
2026.2.23(released)
Mitigation
Upgrade to 2026.2.23 or later once published.
Fix Details
The fix requires and persists nodeId for host=node approval requests and rejects execution when the approving node binding does not match the invoking node.
Fix Commit(s)
- 4a3f8438e527ac371a67fe7ac68a287f0dbe6063
Release Process Note
patched_versions is pre-set to the released version (2026.2.23). This advisory now reflects released fix version 2026.2.23.
OpenClaw thanks @tdjackey for reporting.
Impact
An operator approval for a system.run request could be reused across nodes if the request payload did not carry node identity through approval and execution checks.
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
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-6X2M-HQFW-HVPJ? GHSA-6X2M-HQFW-HVPJ is a medium-severity incorrect authorization vulnerability in openclaw (npm), affecting versions < 2026.2.23. It is fixed in 2026.2.23. 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-6X2M-HQFW-HVPJ? openclaw (npm) versions < 2026.2.23 is affected.
- Is there a fix for GHSA-6X2M-HQFW-HVPJ? Yes. GHSA-6X2M-HQFW-HVPJ is fixed in 2026.2.23. Upgrade to this version or later.
- Is GHSA-6X2M-HQFW-HVPJ exploitable, and should I be worried? Whether GHSA-6X2M-HQFW-HVPJ 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-6X2M-HQFW-HVPJ 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-6X2M-HQFW-HVPJ? Upgrade
openclawto 2026.2.23 or later.