CVE-2026-100599
Received Received - Intake

Command Execution Bypass in OpenClaw Google Meet Node

Publication date: 2026-09-26

Last updated on: 2026-09-26

Assigner: VulnCheck

Description
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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-26
Last Modified
2026-09-26
Generated
2026-09-26
AI Q&A
2026-09-26
EPSS Evaluated
N/A
NVD
CVE-2026-100599
EUVD
EUVD-2026-87381

Affected Vendors & Products

Showing 4 associated CPEs
Vendor Product Version / Range
openclaw openclaw From 2026.5.1 (inc) to 2026.7.0 (inc)
google meet *
openclaw openclaw From 2026.5.1 (inc) to 2026.7.1 (exc)
google googlemeet *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-78 The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

OpenClaw versions 2026.5.1 through 2026.7.0 have a flaw where the googlemeet.chrome command bypasses the configured exec approval path. This allows an attacker with access to invoke the command to execute arbitrary processes on a paired Chrome node without proper authorization. The issue is fixed in version 2026.7.1.

Detection Guidance

Check OpenClaw version with 'openclaw --version' or inspect installed packages. Verify if googlemeet.chrome is in allowed node commands. Inspect system logs for unexpected command executions from Chrome nodes.

Impact Analysis

This vulnerability allows an attacker to execute arbitrary commands on a paired Chrome node, potentially compromising files, credentials, browser profiles, and system availability. It requires the Google Meet plugin to be enabled, a paired Chrome node, and the googlemeet.chrome command to be allowed.

Compliance Impact

This vulnerability could lead to unauthorized execution of processes on paired nodes, potentially exposing sensitive data such as files, credentials, and browser profiles. This may violate compliance requirements under GDPR (data protection) and HIPAA (health information security) due to unauthorized access or disclosure of protected information.

Mitigation Strategies

Upgrade OpenClaw to version 2026.7.1 or later. If unable to upgrade immediately, remove googlemeet.chrome from allowed node commands or disable the Google Meet plugin.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-100599. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart