OpenClaw versions 2026.5.1 through 2026.7.0 fail to enforce the configured exec approval path for the googlemeet.chrome node command. This command accepts audio command arrays from the caller and executes them on a paired Chrome node without passing through the standard system.run approval mechanism. In environments where the Google Meet plugin is enabled and the googlemeet.chrome command is allowed, an agent with the ability to invoke this command can execute arbitrary attacker-selected processes on the paired node. This can impact confidentiality and integrity of files, credentials, browser profiles, and availability of the node. The vulnerability is tracked as CVE-2026-100599 with a CVSS 3.1 score of 8.8 (high severity). The issue is resolved in OpenClaw version 2026.7.1. Workarounds include removing the googlemeet.chrome command from allowed node commands or disabling the Google Meet plugin.

An attacker with permission to invoke the googlemeet.chrome node command can execute arbitrary processes on a paired Chrome node without approval, leading to potential compromise of files, credentials, browser profiles, and system availability on that node. This represents a high-severity risk due to the ability to execute arbitrary code with limited privileges and without user interaction.

A fix is available in OpenClaw version 2026.7.1. Until upgrading, mitigate by removing the googlemeet.chrome command from allowed node commands or disabling the Google Meet plugin. These workarounds prevent exploitation by blocking the vulnerable command or plugin functionality.