<?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://cve.radiocsirt.org</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, 14 Oct 2026 17:13:41 +0000</lastBuildDate>
    <item>
      <title>BREW-openclaw-cli-GHSA-3jx4-q2m7-r496 — OpenClaw: Hardlink alias checks could bypass workspace-only file boundaries in specific configurations</title>
      <link>https://cve.radiocsirt.org/vuln/brew-openclaw-cli-ghsa-3jx4-q2m7-r496</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: openclaw-cli&lt;/p&gt;
&lt;p&gt;### Summary
In certain workspace-restricted configurations, OpenClaw could follow hardlink aliases inside the workspace that reference files outside the workspace boundary.&lt;/p&gt;
&lt;p&gt;By default, `tools.fs.workspaceOnly` is off. This primarily affects deployments that intentionally enable workspace-only filesystem restrictions (and workspace-only `apply_patch` checks).&lt;/p&gt;
&lt;p&gt;### Impact
- Confidentiality: out-of-workspace files could be read through in-workspace hardlink aliases.
- Integrity: out-of-workspace files could be modified through in-workspace hardlink aliases.&lt;/p&gt;
&lt;p&gt;### Affected Packages / Versions
- Package: `openclaw` (npm)
- Latest published version at triage time: `2026.2.24`
- Affected range: `&amp;lt;= 2026.2.24`
- Planned patched version: `2026.2.25`&lt;/p&gt;
&lt;p&gt;### Fix Commit(s)
- `04d91d0319b82fd4de91ed05e9fc5219ff2ab64e` (main)&lt;/p&gt;
&lt;p&gt;### Remediation
OpenClaw now rejects hardlinked final-file aliases during workspace boundary validation for:
- workspace-only path checks (`read` / `write` / `edit`)
- workspace-only `apply_patch` read/write paths
- sandbox mount-root path-safety checks&lt;/p&gt;
&lt;p&gt;Regression tests were added for `apply_patch`, workspace fs tools, and sandbox fs bridge hardlink alias escapes.&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
In certain workspace-restricted configurations, OpenClaw could follow hardlink aliases inside the workspace that reference files outside the workspace boundary.&lt;/p&gt;
&lt;p&gt;By default, `tools.fs.workspaceOnly` is off. This primarily affects deployments that intentionally enable workspace-only filesystem restrictions (and workspace-only `apply_patch` checks).&lt;/p&gt;
&lt;p&gt;### Impact
- Confidentiality: out-of-workspace files could be read through in-workspace hardlink aliases.
- Integrity: out-of-workspace files could be modified through in-workspace hardlink aliases.&lt;/p&gt;
&lt;p&gt;### Affected Packages / Versions
- Package: `openclaw` (npm)
- Latest published version at triage time: `2026.2.24`
- Affected range: `&amp;lt;= 2026.2.24`
- Planned patched version: `2026.2.25`&lt;/p&gt;
&lt;p&gt;### Fix Commit(s)
- `04d91d0319b82fd4de91ed05e9fc5219ff2ab64e` (main)&lt;/p&gt;
&lt;p&gt;### Remediation
OpenClaw now rejects hardlinked final-file aliases during workspace boundary validation for:
- workspace-only path checks (`read` / `write` / `edit`)
- workspace-only `apply_patch` read/write paths
- sandbox mount-root path-safety checks&lt;/p&gt;
&lt;p&gt;Regression tests were added for `apply_patch`, workspace fs tools, and sandbox fs bridge hardlink alias escapes.&lt;/p&gt;
&lt;p&gt;OpenClaw thanks @tdjackey for reporting.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/brew-openclaw-cli-ghsa-3jx4-q2m7-r496</guid>
    </item>
  </channel>
</rss>
