OpenClaw
OpenClaw 2026.5.1 before 2026.7.1 Remote Code Execution via googlemeet.chrome
OpenClaw versions 2026.5.1 through 2026.7.0 fail to apply the configured exec approval path to Google Meet node commands. The googlemeet.chrome command accepts caller-supplied audio command arrays and executes them on a paired node without going through the normal system.run approval flow. In deployments with the Google Meet plugin enabled, a paired Chrome node, and the googlemeet.chrome node command allowed, a tool-enabled agent able to invoke that command can execute attacker-selected processes on the paired node, impacting files, credentials, browser profiles, and availability on that node. The issue is fixed in 2026.7.1; as a workaround, remove googlemeet.chrome from allowed node commands or disable the Google Meet plugin.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 2026.5.1, < 2026.7.1
Fixed in 2026.7.1
Mitigation
Upgrade OpenClaw to 2026.7.1 or later.
References
- Vendor advisory github.com/openclaw/openclaw/security/advisori…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.