https://db.gcve.eu/rss/recent/all/10 Most recent entries from all 2026-09-30T03:58:43.519056+00:00 Vulnerability-Lookup info@gcve.eu python-feedgen Contains only the most 10 recent entries. https://db.gcve.eu/vuln/brew-openclaw-cli-cve-2026-28473 BREW-openclaw-cli-CVE-2026-28473 — OpenClaw authorization bypass: operator.write can resolve exec approvals via chat.send -> /approve 2026-09-30T03:58:43.520666+00:00

Affected: Homebrew: openclaw-cli

## Summary

### What this means (plain language)

If you give a client “chat/write” access to the gateway (`operator.write`) but you do not intend to let that client approve exec requests (`operator.approvals`), affected versions could still let that client approve/deny a pending exec approval by sending the `/approve` chat command.

This is mainly relevant for shared or multi-client setups where different tokens are intentionally scoped differently. Single-operator installs are typically less impacted.

### Technical summary

A gateway client authenticated with a device token scoped only to `operator.write` (without `operator.approvals`) could approve/deny pending exec approval requests by sending a chat message containing the built-in `/approve` command.

`exec.approval.resolve` is correctly scoped to `operator.approvals` for direct RPC calls, but the `/approve` command path invoked it via an internal privileged gateway client.

## Affected Packages / Versions

- `openclaw` (npm): `< 2026.2.2`

## Fix

- Fixed in `openclaw` `2026.2.2`. - Fix commit(s): `efe2a464afcff55bb5a95b959e6bd9ec0fef086e`. - Change: when `/approve` is invoked from gateway clients (webchat/internal channel), it now requires the requesting client to have `operator.approvals` (or `operator.admin`).

## Workarounds

- Upgrade to `openclaw >= 2026.2.2`. - If you cannot upgrade: avoid issuing write-only device tokens to untrusted clients; disable text commands (`commands.text=false`) or restrict access to…

 https://db.gcve.eu/vuln/cve-2026-28473 CVE-2026-28473 — OpenClaw < 2026.2.2 - Authorization Bypass via /approve Chat Command 2026-09-30T03:58:43.520795+00:00

Affected: OpenClaw

OpenClaw versions prior to 2026.2.2 contain an authorization bypass vulnerability where clients with operator.write scope can approve or deny exec approval requests by sending the /approve chat command. The /approve command path invokes exec.approval.resolve through an internal privileged gateway client, bypassing the operator.approvals permission check that protects direct RPC calls.