Skip to main content
VulnerabilityPublished

CVE-2026-100599: OpenClaw versions 2026.5.1 through 2026.7.0 fail to apply the configured exec approval path to

Affects openclawSource GCVE Database

0
Compare

Not known to be exploited · CVSS 8.8 High : upgrade to 2026.7.1 soon.

Data as of 9 Nov 2026, 23:24 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2026.7.1
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.

What to do

Upgrade openclaw/openclaw to 2026.7.1.

Affected software

ProductAffectedFixed in
GitHubopenclaw/openclawpkg:github/openclaw/openclawOther threatsAffected
  • >=2026.5.1 <2026.7.1
Fixed in
  • 2026.7.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

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.

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.

References

Community reviews

Loading reviews…