https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 05 Oct 2026 16:26:33 +0000 https://vulnerability.circl.lu/vuln/brew-openclaw-cli-ghsa-2ch6-x3g4-7759 <p><strong>Affected:</strong> Homebrew: openclaw-cli</p> <p>### Summary `commands.allowFrom` is documented as a sender authorization allowlist for commands/directives, but command authorization could include `ctx.From` (conversation identity) as a sender candidate.</p> <p>When `commands.allowFrom` contained conversation-like identifiers (for example Discord `channel:&lt;id&gt;` or WhatsApp group JIDs), command/directive authorization could be granted to participants in that conversation instead of only the intended sender identity.</p> <p>### Affected Packages / Versions - Package: `openclaw` (npm) - Affected versions: `&lt;= 2026.2.22-2` - Patched version: `2026.2.23` (released)</p> <p>### Details Root cause: `resolveSenderCandidates()` in `src/auto-reply/command-auth.ts` always included `ctx.From` in candidate evaluation used by `commands.allowFrom` authorization checks.</p> <p>`ctx.From` is sender-like in some direct-message contexts, but conversation-like in channel/group/thread contexts. This mixed principal handling allowed conversation identifiers to satisfy sender-only authorization.</p> <p>### Impact In affected versions, command/directive authorization could become broader than intended when operators configured `commands.allowFrom` with conversation identifiers, allowing unintended users in that conversation to run command-only/directive-only flows.</p> <p>### Fix Main branch now treats `commands.allowFrom` as sender-only: - `ctx.From` is no longer included as a general sender candidate. - `ctx.From` is only used as fallback when sender fields are absent and the valu…</p> <p><strong>Affected:</strong> Homebrew: openclaw-cli</p> <p>### Summary `commands.allowFrom` is documented as a sender authorization allowlist for commands/directives, but command authorization could include `ctx.From` (conversation identity) as a sender candidate.</p> <p>When `commands.allowFrom` contained conversation-like identifiers (for example Discord `channel:&lt;id&gt;` or WhatsApp group JIDs), command/directive authorization could be granted to participants in that conversation instead of only the intended sender identity.</p> <p>### Affected Packages / Versions - Package: `openclaw` (npm) - Affected versions: `&lt;= 2026.2.22-2` - Patched version: `2026.2.23` (released)</p> <p>### Details Root cause: `resolveSenderCandidates()` in `src/auto-reply/command-auth.ts` always included `ctx.From` in candidate evaluation used by `commands.allowFrom` authorization checks.</p> <p>`ctx.From` is sender-like in some direct-message contexts, but conversation-like in channel/group/thread contexts. This mixed principal handling allowed conversation identifiers to satisfy sender-only authorization.</p> <p>### Impact In affected versions, command/directive authorization could become broader than intended when operators configured `commands.allowFrom` with conversation identifiers, allowing unintended users in that conversation to run command-only/directive-only flows.</p> <p>### Fix Main branch now treats `commands.allowFrom` as sender-only: - `ctx.From` is no longer included as a general sender candidate. - `ctx.From` is only used as fallback when sender fields are absent and the valu…</p> https://vulnerability.circl.lu/vuln/brew-openclaw-cli-ghsa-2ch6-x3g4-7759