A weakness in the approval context binding of OpenClaw’s system.run function for host=node allows an attacker who has an approval ID to reuse a previously approved request while changing environment variables. This bypasses the execution‑integrity controls that normally enforce that a specific approval governs a specific workflow execution, potentially enabling unauthorized code paths or data manipulation within approval‑enabled pipelines.

All OpenClaw versions before 2026.2.26 running on Node.js are affected. No further sub‑version detail is provided, so any deployment of OpenClaw that has not yet been upgraded to 2026.2.26 or newer is at risk.

The CVSS score is 2.0, indicating a low severity assessment in the vendor’s guidelines, and no EPSS score is available. The vulnerability is not listed in the CISA KEV catalog. Exploitation requires possession of an existing approval ID and the ability to modify environmental inputs. While the overall risk appears modest, the abuse of the integrity controls could allow escalation of privileges inside the workflow environment. Therefore, the threat is significant for systems that rely heavily on approval enforcement and expose approval IDs to potential attackers.