<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Mon, 28 Sep 2026 14:29:56 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-44991 — OpenClaw &lt; 2026.4.21 - Authorization Bypass in Owner-Enforced Commands via Wildcard Channel Senders</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-44991</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; OpenClaw&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; OpenClaw&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-44991</guid>
    </item>
    <item>
      <title>GHSA-c28g-vh7m-fm7v — OpenClaw: Owner-enforced commands could accept wildcard channel senders as command owners</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-c28g-vh7m-fm7v</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: openclaw&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;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:&lt;/p&gt;
&lt;p&gt;- a channel plugin declared `commands.enforceOwnerForCommands: true`;
- the channel accepted wildcard inbound senders with `allowFrom: [&amp;#34;*&amp;#34;]`;
- no explicit `commands.ownerAllowFrom` was configured.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;## Affected Packages / Versions&lt;/p&gt;
&lt;p&gt;- Package: `openclaw` on npm
- Affected versions: `&amp;lt;= 2026.4.20`
- Patched version: `2026.4.21`&lt;/p&gt;
&lt;p&gt;The latest public release, `2026.4.21`, contains the fix.&lt;/p&gt;
&lt;p&gt;## Patches&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;Fix commits:&lt;/p&gt;
&lt;p&gt;- `2aa93d44a1b2c7058c371f261fda2b5d4de4a882` on `main`
- `995febb7b1e811ff6a1df5b18c22de94103f4c9f` in the `2026.4.21` release line&lt;/p&gt;
&lt;p&gt;## Workarounds&lt;/p&gt;
&lt;p&gt;Upgrade to `openclaw@2026.4.21` or later. Before upgrading, avoid wildcard/open-DM sender policy on owner-enforced channels, o…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: openclaw&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;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:&lt;/p&gt;
&lt;p&gt;- a channel plugin declared `commands.enforceOwnerForCommands: true`;
- the channel accepted wildcard inbound senders with `allowFrom: [&amp;#34;*&amp;#34;]`;
- no explicit `commands.ownerAllowFrom` was configured.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;## Affected Packages / Versions&lt;/p&gt;
&lt;p&gt;- Package: `openclaw` on npm
- Affected versions: `&amp;lt;= 2026.4.20`
- Patched version: `2026.4.21`&lt;/p&gt;
&lt;p&gt;The latest public release, `2026.4.21`, contains the fix.&lt;/p&gt;
&lt;p&gt;## Patches&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;Fix commits:&lt;/p&gt;
&lt;p&gt;- `2aa93d44a1b2c7058c371f261fda2b5d4de4a882` on `main`
- `995febb7b1e811ff6a1df5b18c22de94103f4c9f` in the `2026.4.21` release line&lt;/p&gt;
&lt;p&gt;## Workarounds&lt;/p&gt;
&lt;p&gt;Upgrade to `openclaw@2026.4.21` or later. Before upgrading, avoid wildcard/open-DM sender policy on owner-enforced channels, o…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-c28g-vh7m-fm7v</guid>
    </item>
  </channel>
</rss>
