{
  "id": "CVE-2026-100599",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-100599",
  "published_at": "2026-09-26T02:19:18.983Z",
  "title": "OpenClaw 2026.5.1 before 2026.7.1 Remote Code Execution via googlemeet.chrome",
  "vendor": "OpenClaw",
  "product": "OpenClaw",
  "cvss": {
    "score": 8.8,
    "source": "cna",
    "vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
  },
  "kev": {
    "in_kev": false,
    "added_at": null,
    "days_after_publication": null
  },
  "first_poc": null,
  "poc_repo_count": 0,
  "exploit_count": 0,
  "suspicious_repo_count": 0,
  "edge_device": null,
  "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.",
  "cwe": "CWE-78",
  "cvss_by_source": {
    "cna": 8.8
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "OpenClaw",
        "product": "OpenClaw",
        "ranges": [
          "\u003e= 2026.5.1, \u003c 2026.7.1"
        ],
        "fixed_in": [
          "2026.7.1"
        ]
      }
    ],
    "upgrade": [
      "Upgrade OpenClaw to 2026.7.1 or later."
    ],
    "references": [
      {
        "kind": "Vendor advisory",
        "url": "https://github.com/openclaw/openclaw/security/advisories/GHSA-224w-vfr9-h35c"
      }
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
