<?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>Thu, 08 Oct 2026 13:34:01 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-32038 — OpenClaw - Sandbox Network Isolation Bypass via docker.network=container Parameter</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-32038</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; OpenClaw&lt;/p&gt;
&lt;p&gt;OpenClaw before 2026.2.24 contains a sandbox network isolation bypass vulnerability that allows trusted operators to join another container&amp;#39;s network namespace. Attackers can configure the docker.network parameter with container:&amp;lt;id&amp;gt; values to reach services in target container namespaces and bypass network hardening controls.&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.2.24 contains a sandbox network isolation bypass vulnerability that allows trusted operators to join another container&amp;#39;s network namespace. Attackers can configure the docker.network parameter with container:&amp;lt;id&amp;gt; values to reach services in target container namespaces and bypass network hardening controls.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-32038</guid>
    </item>
    <item>
      <title>GHSA-ww6v-v748-x7g9 — OpenClaw has a sandbox network isolation bypass via docker.network=container:&lt;id&gt;</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-ww6v-v748-x7g9</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: openclaw&lt;/p&gt;
&lt;p&gt;### Summary
In `openclaw@2026.2.23`, sandbox network hardening blocks `network=host` but still allows `network=container:&amp;lt;id&amp;gt;`.&lt;/p&gt;
&lt;p&gt;This can let a sandbox join another container&amp;#39;s network namespace and reach services available in that namespace.&lt;/p&gt;
&lt;p&gt;### Preconditions and Trust Model Context
This issue requires a trusted-operator configuration path (for example setting `agents.defaults.sandbox.docker.network` in gateway config). It is not an unauthenticated remote exploit by itself.&lt;/p&gt;
&lt;p&gt;### Details
Current validation blocks only `host`, while forwarding other values to Docker create args:&lt;/p&gt;
&lt;p&gt;- `validateNetworkMode(network)` only rejects values in `BLOCKED_NETWORK_MODES = {&amp;#34;host&amp;#34;}`.
- `buildSandboxCreateArgs(...)` validates then forwards `cfg.network` into `--network`.
- Browser sandbox helper also treats `container:` as an accepted mode in network preparation.&lt;/p&gt;
&lt;p&gt;Effective behavior:&lt;/p&gt;
&lt;p&gt;- `host` -&amp;gt; blocked
- `container:&amp;lt;id&amp;gt;` -&amp;gt; accepted and forwarded&lt;/p&gt;
&lt;p&gt;### Impact
Type: sandbox network isolation hardening bypass.&lt;/p&gt;
&lt;p&gt;Practical impact depends on deployment:&lt;/p&gt;
&lt;p&gt;- Requires ability to influence trusted sandbox network config.
- Higher impact when a target container exposes privileged/internal network reachability.&lt;/p&gt;
&lt;p&gt;### Remediation
Block namespace-join style network modes (including `container:&amp;lt;id&amp;gt;`) for sandbox containers, and keep strict allowlisting for safe network modes.&lt;/p&gt;
&lt;p&gt;### Patch Status
Fixed on `main` in commit `14b6eea6e`:
https://github.com/openclaw/openclaw/commit/14b6eea6e&lt;/p&gt;
&lt;p&gt;Follow-up refact…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: openclaw&lt;/p&gt;
&lt;p&gt;### Summary
In `openclaw@2026.2.23`, sandbox network hardening blocks `network=host` but still allows `network=container:&amp;lt;id&amp;gt;`.&lt;/p&gt;
&lt;p&gt;This can let a sandbox join another container&amp;#39;s network namespace and reach services available in that namespace.&lt;/p&gt;
&lt;p&gt;### Preconditions and Trust Model Context
This issue requires a trusted-operator configuration path (for example setting `agents.defaults.sandbox.docker.network` in gateway config). It is not an unauthenticated remote exploit by itself.&lt;/p&gt;
&lt;p&gt;### Details
Current validation blocks only `host`, while forwarding other values to Docker create args:&lt;/p&gt;
&lt;p&gt;- `validateNetworkMode(network)` only rejects values in `BLOCKED_NETWORK_MODES = {&amp;#34;host&amp;#34;}`.
- `buildSandboxCreateArgs(...)` validates then forwards `cfg.network` into `--network`.
- Browser sandbox helper also treats `container:` as an accepted mode in network preparation.&lt;/p&gt;
&lt;p&gt;Effective behavior:&lt;/p&gt;
&lt;p&gt;- `host` -&amp;gt; blocked
- `container:&amp;lt;id&amp;gt;` -&amp;gt; accepted and forwarded&lt;/p&gt;
&lt;p&gt;### Impact
Type: sandbox network isolation hardening bypass.&lt;/p&gt;
&lt;p&gt;Practical impact depends on deployment:&lt;/p&gt;
&lt;p&gt;- Requires ability to influence trusted sandbox network config.
- Higher impact when a target container exposes privileged/internal network reachability.&lt;/p&gt;
&lt;p&gt;### Remediation
Block namespace-join style network modes (including `container:&amp;lt;id&amp;gt;`) for sandbox containers, and keep strict allowlisting for safe network modes.&lt;/p&gt;
&lt;p&gt;### Patch Status
Fixed on `main` in commit `14b6eea6e`:
https://github.com/openclaw/openclaw/commit/14b6eea6e&lt;/p&gt;
&lt;p&gt;Follow-up refact…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-ww6v-v748-x7g9</guid>
    </item>
  </channel>
</rss>
