https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 11 Oct 2026 14:48:34 +0000 https://db.gcve.eu/vuln/ghsa-hfpr-jhpq-x4rm <p><strong>Affected:</strong> npm: openclaw</p> <p>### Summary A gateway client authenticated with `operator.write` could route `/config set` or `/config unset` through `chat.send` and reach persistent config mutation even though direct config RPC methods are admin-scoped.</p> <p>### Affected Packages / Versions - Package: `openclaw` (npm) - Latest published vulnerable version: `2026.3.2` - Affected range: `&lt;= 2026.3.2` - Patched in: `2026.3.7`</p> <p>### Details Before the fix, `chat.send` ran slash commands in an internal gateway-chat context with `CommandAuthorized: true`, and `/config` write paths only checked command authorization plus `commands.config` / `channels.&lt;provider&gt;.configWrites` gates. That allowed an authenticated `operator.write` gateway client to bridge into persistent config writes even though direct `config.*` RPC methods remain `operator.admin` scoped.</p> <p>The fix keeps command functionality intact while restoring the intended scope boundary: - persistent `/config set|unset` writes routed through gateway `chat.send` now require `operator.admin` - read-only `/config show` remains available to normal write-scoped gateway clients - normal messaging-channel `/config` behavior remains unchanged</p> <p>### Impact This is a real authorization mismatch, but exploitability requires an already authenticated gateway client with `operator.write`, `chat.send` access, and `/config` command support enabled. Maintainer severity is set to medium because the bug is a scoped control-plane privilege mismatch rather than a broad unauthenticated…</p> <p><strong>Affected:</strong> npm: openclaw</p> <p>### Summary A gateway client authenticated with `operator.write` could route `/config set` or `/config unset` through `chat.send` and reach persistent config mutation even though direct config RPC methods are admin-scoped.</p> <p>### Affected Packages / Versions - Package: `openclaw` (npm) - Latest published vulnerable version: `2026.3.2` - Affected range: `&lt;= 2026.3.2` - Patched in: `2026.3.7`</p> <p>### Details Before the fix, `chat.send` ran slash commands in an internal gateway-chat context with `CommandAuthorized: true`, and `/config` write paths only checked command authorization plus `commands.config` / `channels.&lt;provider&gt;.configWrites` gates. That allowed an authenticated `operator.write` gateway client to bridge into persistent config writes even though direct `config.*` RPC methods remain `operator.admin` scoped.</p> <p>The fix keeps command functionality intact while restoring the intended scope boundary: - persistent `/config set|unset` writes routed through gateway `chat.send` now require `operator.admin` - read-only `/config show` remains available to normal write-scoped gateway clients - normal messaging-channel `/config` behavior remains unchanged</p> <p>### Impact This is a real authorization mismatch, but exploitability requires an already authenticated gateway client with `operator.write`, `chat.send` access, and `/config` command support enabled. Maintainer severity is set to medium because the bug is a scoped control-plane privilege mismatch rather than a broad unauthenticated…</p> https://db.gcve.eu/vuln/ghsa-hfpr-jhpq-x4rm