CVE-2026-100599: OpenClaw 2026.5.1 before 2026.7.1 Remote Code Execution via googlemeet.chrome

Published Sep 26, 2026
·
Updated

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 Software

1 affected component
OpenClaw OpenClaw>=2026.5.1<=2026.7.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade OpenClaw to a version that resolves this vulnerability.

    Fixed in 2026.7.1
  2. Configuration

    As a workaround, remove googlemeet.chrome from allowed node commands or disable the Google Meet plugin.

    OpenClaw Google Meet integration googlemeet.chrome allowed node command / Google Meet plugin = disabled

Event History

Sep 26, 2026
CVE Published
via MITRE·02:19 AM
Data Sourced
via MITRE·02:19 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·03:17 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed?

Exposure requires the Google Meet plugin to be enabled, a paired Chrome node, and googlemeet.chrome to be allowed as a node command. A tool-enabled agent must also be able to invoke that command.

2

What access does an attacker need to exploit this?

An attacker needs a path to cause a tool-enabled agent to invoke googlemeet.chrome with attacker-controlled audio command arrays. The vulnerable command executes those supplied processes on the paired node without the normal system.run approval flow.

3

What can be affected on the paired node?

Successful exploitation can affect files, credentials, browser profiles, and the availability of the paired node. The vulnerability is rated high with high confidentiality, integrity, and availability impact.

4

What can be done before upgrading?

Remove googlemeet.chrome from the allowed node commands or disable the Google Meet plugin. These workarounds prevent use of the vulnerable command path.

5

Which versions need remediation?

OpenClaw versions 2026.5.1 through 2026.7.0 are affected. The issue is fixed in version 2026.7.1.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203