<?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>Wed, 30 Sep 2026 12:37:21 +0000</lastBuildDate>
    <item>
      <title>BREW-openclaw-cli-GHSA-8mf7-vv8w-hjr2 — OpenClaw's tools.exec.safeBins generic fallback allowed interpreter-style inline payload execution in allowlist mode</title>
      <link>https://vulnerability.circl.lu/vuln/brew-openclaw-cli-ghsa-8mf7-vv8w-hjr2</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: openclaw-cli&lt;/p&gt;
&lt;p&gt;### Summary
When `tools.exec.safeBins` contained a binary without an explicit safe-bin profile, OpenClaw used a permissive generic fallback profile. In allowlist mode, that could let interpreter-style binaries (for example `python3`, `node`, `ruby`) execute inline payloads via flags like `-c`.&lt;/p&gt;
&lt;p&gt;This requires explicit operator configuration to add such binaries to `safeBins`, so impact is limited to non-default/misconfigured deployments.&lt;/p&gt;
&lt;p&gt;### Affected Packages / Versions
- Package: `openclaw` (npm)
- Affected versions: `&amp;lt;= 2026.2.21-2`
- Patched in code: `&amp;gt;= 2026.2.22` (planned next npm release)&lt;/p&gt;
&lt;p&gt;### Fix
- Remove generic safe-bin fallback during allowlist evaluation.
- Require explicit safe-bin profiles for `safeBins` entries.
- Add configurable `tools.exec.safeBinProfiles` (global + per-agent) for safe custom binaries.
- Update docs to clearly separate `safeBins` from command allowlist semantics.&lt;/p&gt;
&lt;p&gt;### Fix Commit(s)
- `47c3f742b6c488be26dd7b9636dbbb8676089154`&lt;/p&gt;
&lt;p&gt;### Release Process Note
`patched_versions` is pre-set to the planned next release (`&amp;gt;= 2026.2.22`) so once that npm release is published, the advisory can be published directly without further metadata edits.&lt;/p&gt;
&lt;p&gt;OpenClaw thanks @tdjackey for reporting.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: openclaw-cli&lt;/p&gt;
&lt;p&gt;### Summary
When `tools.exec.safeBins` contained a binary without an explicit safe-bin profile, OpenClaw used a permissive generic fallback profile. In allowlist mode, that could let interpreter-style binaries (for example `python3`, `node`, `ruby`) execute inline payloads via flags like `-c`.&lt;/p&gt;
&lt;p&gt;This requires explicit operator configuration to add such binaries to `safeBins`, so impact is limited to non-default/misconfigured deployments.&lt;/p&gt;
&lt;p&gt;### Affected Packages / Versions
- Package: `openclaw` (npm)
- Affected versions: `&amp;lt;= 2026.2.21-2`
- Patched in code: `&amp;gt;= 2026.2.22` (planned next npm release)&lt;/p&gt;
&lt;p&gt;### Fix
- Remove generic safe-bin fallback during allowlist evaluation.
- Require explicit safe-bin profiles for `safeBins` entries.
- Add configurable `tools.exec.safeBinProfiles` (global + per-agent) for safe custom binaries.
- Update docs to clearly separate `safeBins` from command allowlist semantics.&lt;/p&gt;
&lt;p&gt;### Fix Commit(s)
- `47c3f742b6c488be26dd7b9636dbbb8676089154`&lt;/p&gt;
&lt;p&gt;### Release Process Note
`patched_versions` is pre-set to the planned next release (`&amp;gt;= 2026.2.22`) so once that npm release is published, the advisory can be published directly without further metadata edits.&lt;/p&gt;
&lt;p&gt;OpenClaw thanks @tdjackey for reporting.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/brew-openclaw-cli-ghsa-8mf7-vv8w-hjr2</guid>
    </item>
  </channel>
</rss>
