Integrity Guardrail Weakness in OpenClaw Package: Approval Context-Binding Issue
Summary
GHSA-hjvp-qhm6-wrh2: OpenClaw Node system.run approval context-binding weakness in approval-enabled host=node flows. Affects openclaw versions < 2026.2.26. Fixed in 2026.2.26. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
OpenClaw is an open-source package designed for managing workflows in Node.js environments, particularly focusing on execution integrity through approval mechanisms. It allows users to define and control execution paths, ensuring that commands are executed under specific conditions. However, a recent vulnerability has been identified that affects the integrity of approval processes in certain configurations.
Vulnerability Detail
The vulnerability arises in approval-enabled workflows using 'host=node', where 'system.run' approvals lack a strict, versioned execution-context binding. This means that a previously approved request could potentially be reused with altered environmental inputs, undermining the integrity of the execution process. The issue is particularly concerning for setups that rely on these approvals as a security measure, as it could lead to unauthorized command execution under certain conditions.
How To Fix
Latest published version: 2026.10.6 as of 22 Oct 2026
npm install openclaw@2026.10.6Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.
If you need the minimum change
2026.2.26
This is the first release that contains the fix.
npm install openclaw@2026.2.26Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
Currently, there are no specific workarounds mentioned for this vulnerability. It is recommended to apply the patch as soon as it becomes available to mitigate any risks associated with this issue.
Conclusion
In summary, the OpenClaw package has a vulnerability related to approval context-binding in 'host=node' workflows that could compromise execution integrity. Users are advised to update to version 2026.2.26 to mitigate this risk. Regular monitoring and prompt updates are essential for maintaining application security.
See every vulnerability recorded for openclaw →
FAQ
The vulnerability has a CVSS score of 5.5, indicating a moderate level of severity.
If your application uses OpenClaw with approval-enabled workflows, this vulnerability could allow unauthorized command execution if an approval ID is reused with altered environmental inputs.
You can check if your application is affected by using the Vulert playground at Vulert Scanner, which analyzes your package-lock.json for vulnerabilities without requiring any signup.
While there are no specific workarounds, it is crucial to monitor your application for any unusual behavior and plan to update to the patched version as soon as possible.
The vulnerability was reported by a user identified as @tdjackey, highlighting the importance of community involvement in maintaining software security.
References
Related vulnerabilities
Recent vulnerabilities recorded for openclaw.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Follow Vulert in Google
Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.