<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-05T02:24:35.161472+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/brew-openclaw-cli-cve-2026-44991</id>
    <title>BREW-openclaw-cli-CVE-2026-44991 — OpenClaw: Owner-enforced commands could accept wildcard channel senders as command owners</title>
    <updated>2026-10-05T02:24:35.164477+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Homebrew: openclaw-cli</p>
<p>## Impact</p>
<p>OpenClaw deployments before `2026.4.21` could treat a non-owner sender as authorized for owner-enforced slash commands when all of the following were true:</p>
<p>- a channel plugin declared `commands.enforceOwnerForCommands: true`;
- the channel accepted wildcard inbound senders with `allowFrom: ["*"]`;
- no explicit `commands.ownerAllowFrom` was configured.</p>
<p>In that state, `src/auto-reply/command-auth.ts` reused the channel inbound wildcard as part of the command-owner decision. A sender who was not the owner could therefore pass the owner-command gate for commands such as `/send`, `/config`, or `/debug` on the affected channel.</p>
<p>The issue is limited to the command-owner authorization axis. It does not by itself grant owner-only tool access, host/sandbox access, or gateway administrator scope.</p>
<p>## Affected Packages / Versions</p>
<p>- Package: `openclaw` on npm
- Affected versions: `&lt;= 2026.4.20`
- Patched version: `2026.4.21`</p>
<p>The latest public release, `2026.4.21`, contains the fix.</p>
<p>## Patches</p>
<p>The fix requires a concrete owner identity or internal operator-admin scope when a plugin enforces owner-only commands. Wildcard channel `allowFrom` no longer implies wildcard command ownership.</p>
<p>Fix commits:</p>
<p>- `2aa93d44a1b2c7058c371f261fda2b5d4de4a882` on `main`
- `995febb7b1e811ff6a1df5b18c22de94103f4c9f` in the `2026.4.21` release line</p>
<p>## Workarounds</p>
<p>Upgrade to `openclaw@2026.4.21` or later. Before upgrading, avoid wildcard/open-DM sender policy on owner-enforced channels, o…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/brew-openclaw-cli-cve-2026-44991"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-309977</id>
    <title>EUVD-2026-309977</title>
    <updated>2026-10-05T02:24:35.164548+00:00</updated>
    <content>EUVD-2026-309977</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-309977"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-44991</id>
    <title>fkie_cve-2026-44991</title>
    <updated>2026-10-05T02:24:35.164565+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>OpenClaw before 2026.4.21 contains an authorization bypass vulnerability in command-auth.ts that allows non-owner senders to execute owner-enforced slash commands when wildcard inbound senders are configured without explicit owner allowFrom settings. Attackers can exploit this by sending commands like /send, /config, or /debug on affected channels to bypass owner-only command authorization checks.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-44991"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-c28g-vh7m-fm7v</id>
    <title>GHSA-c28g-vh7m-fm7v — OpenClaw: Owner-enforced commands could accept wildcard channel senders as command owners</title>
    <updated>2026-10-05T02:24:35.164588+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: openclaw</p>
<p>## Impact</p>
<p>OpenClaw deployments before `2026.4.21` could treat a non-owner sender as authorized for owner-enforced slash commands when all of the following were true:</p>
<p>- a channel plugin declared `commands.enforceOwnerForCommands: true`;
- the channel accepted wildcard inbound senders with `allowFrom: ["*"]`;
- no explicit `commands.ownerAllowFrom` was configured.</p>
<p>In that state, `src/auto-reply/command-auth.ts` reused the channel inbound wildcard as part of the command-owner decision. A sender who was not the owner could therefore pass the owner-command gate for commands such as `/send`, `/config`, or `/debug` on the affected channel.</p>
<p>The issue is limited to the command-owner authorization axis. It does not by itself grant owner-only tool access, host/sandbox access, or gateway administrator scope.</p>
<p>## Affected Packages / Versions</p>
<p>- Package: `openclaw` on npm
- Affected versions: `&lt;= 2026.4.20`
- Patched version: `2026.4.21`</p>
<p>The latest public release, `2026.4.21`, contains the fix.</p>
<p>## Patches</p>
<p>The fix requires a concrete owner identity or internal operator-admin scope when a plugin enforces owner-only commands. Wildcard channel `allowFrom` no longer implies wildcard command ownership.</p>
<p>Fix commits:</p>
<p>- `2aa93d44a1b2c7058c371f261fda2b5d4de4a882` on `main`
- `995febb7b1e811ff6a1df5b18c22de94103f4c9f` in the `2026.4.21` release line</p>
<p>## Workarounds</p>
<p>Upgrade to `openclaw@2026.4.21` or later. Before upgrading, avoid wildcard/open-DM sender policy on owner-enforced channels, o…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-c28g-vh7m-fm7v"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1242</id>
    <title>WID-SEC-W-2026-1242 — OpenClaw: Mehrere Schwachstellen</title>
    <updated>2026-10-05T02:24:35.164628+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein Angreifer kann mehrere Schwachstellen in OpenClaw ausnutzen, um Sicherheitsvorkehrungen zu umgehen oder vertrauliche Informationen offenzulegen.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1242"/>
  </entry>
</feed>
