<?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 21:34:57 +0000</lastBuildDate>
    <item>
      <title>BREW-openclaw-cli-CVE-2026-27002 — OpenClaw: Docker container escape via unvalidated bind mount config injection</title>
      <link>https://vulnerability.circl.lu/vuln/brew-openclaw-cli-cve-2026-27002</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: openclaw-cli&lt;/p&gt;
&lt;p&gt;## Summary
A configuration injection issue in the Docker tool sandbox could allow dangerous Docker options (bind mounts, host networking, unconfined profiles) to be applied, enabling container escape or host data access.&lt;/p&gt;
&lt;p&gt;## Affected Packages / Versions
- Package: `openclaw` (npm)
- Affected versions: `&amp;lt;= 2026.2.14`
- Fixed version: `&amp;gt;= 2026.2.15` (next release)&lt;/p&gt;
&lt;p&gt;## Impact
If an attacker can influence sandbox Docker configuration (or an operator pastes untrusted config), they may be able to:
- mount sensitive host paths (e.g. `/etc`, `/proc`, `/sys`, `/dev`, Docker socket)
- use `network=host` to bypass container network isolation
- use `seccompProfile=unconfined` / `apparmorProfile=unconfined` to weaken isolation&lt;/p&gt;
&lt;p&gt;This can lead to host secret exfiltration or full host control (via Docker socket exposure).&lt;/p&gt;
&lt;p&gt;## Fix
OpenClaw now blocks dangerous sandbox Docker settings:
- runtime enforcement when building `docker create` args
- config-schema validation for `network=host`, `seccompProfile=unconfined`, `apparmorProfile=unconfined`
- security audit findings to surface dangerous sandbox docker config&lt;/p&gt;
&lt;p&gt;## Workarounds
- Do not configure `agents.*.sandbox.docker.binds` to mount system directories or Docker socket paths.
- Keep `agents.*.sandbox.docker.network` at `none` (default) or `bridge`.
- Do not use `unconfined` for seccomp/AppArmor profiles.&lt;/p&gt;
&lt;p&gt;## Fix Commit(s)
- 887b209db47f1f9322fead241a1c0b043fd38339
- 1b6704ef5800152c777ea52b77aa2c8a46c13705 (docs)&lt;/p&gt;
&lt;p&gt;## Release Process Note
T…&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
A configuration injection issue in the Docker tool sandbox could allow dangerous Docker options (bind mounts, host networking, unconfined profiles) to be applied, enabling container escape or host data access.&lt;/p&gt;
&lt;p&gt;## Affected Packages / Versions
- Package: `openclaw` (npm)
- Affected versions: `&amp;lt;= 2026.2.14`
- Fixed version: `&amp;gt;= 2026.2.15` (next release)&lt;/p&gt;
&lt;p&gt;## Impact
If an attacker can influence sandbox Docker configuration (or an operator pastes untrusted config), they may be able to:
- mount sensitive host paths (e.g. `/etc`, `/proc`, `/sys`, `/dev`, Docker socket)
- use `network=host` to bypass container network isolation
- use `seccompProfile=unconfined` / `apparmorProfile=unconfined` to weaken isolation&lt;/p&gt;
&lt;p&gt;This can lead to host secret exfiltration or full host control (via Docker socket exposure).&lt;/p&gt;
&lt;p&gt;## Fix
OpenClaw now blocks dangerous sandbox Docker settings:
- runtime enforcement when building `docker create` args
- config-schema validation for `network=host`, `seccompProfile=unconfined`, `apparmorProfile=unconfined`
- security audit findings to surface dangerous sandbox docker config&lt;/p&gt;
&lt;p&gt;## Workarounds
- Do not configure `agents.*.sandbox.docker.binds` to mount system directories or Docker socket paths.
- Keep `agents.*.sandbox.docker.network` at `none` (default) or `bridge`.
- Do not use `unconfined` for seccomp/AppArmor profiles.&lt;/p&gt;
&lt;p&gt;## Fix Commit(s)
- 887b209db47f1f9322fead241a1c0b043fd38339
- 1b6704ef5800152c777ea52b77aa2c8a46c13705 (docs)&lt;/p&gt;
&lt;p&gt;## Release Process Note
T…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/brew-openclaw-cli-cve-2026-27002</guid>
    </item>
    <item>
      <title>CVE-2026-27002 — OpenClaw: Docker container escape via unvalidated bind mount config injection</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-27002</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openclaw&lt;/p&gt;
&lt;p&gt;OpenClaw is a personal AI assistant. Prior to version 2026.2.15, a configuration injection issue in the Docker tool sandbox could allow dangerous Docker options (bind mounts, host networking, unconfined profiles) to be applied, enabling container escape or host data access. OpenClaw 2026.2.15 blocks dangerous sandbox Docker settings and includes runtime enforcement when building `docker create` args; config-schema validation for `network=host`, `seccompProfile=unconfined`, `apparmorProfile=unconfined`; and security audit findings to surface dangerous sandbox docker config. As a workaround, do not configure `agents.*.sandbox.docker.binds` to mount system directories or Docker socket paths, keep `agents.*.sandbox.docker.network` at `none` (default) or `bridge`, and do not use `unconfined` for seccomp/AppArmor profiles.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openclaw&lt;/p&gt;
&lt;p&gt;OpenClaw is a personal AI assistant. Prior to version 2026.2.15, a configuration injection issue in the Docker tool sandbox could allow dangerous Docker options (bind mounts, host networking, unconfined profiles) to be applied, enabling container escape or host data access. OpenClaw 2026.2.15 blocks dangerous sandbox Docker settings and includes runtime enforcement when building `docker create` args; config-schema validation for `network=host`, `seccompProfile=unconfined`, `apparmorProfile=unconfined`; and security audit findings to surface dangerous sandbox docker config. As a workaround, do not configure `agents.*.sandbox.docker.binds` to mount system directories or Docker socket paths, keep `agents.*.sandbox.docker.network` at `none` (default) or `bridge`, and do not use `unconfined` for seccomp/AppArmor profiles.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-27002</guid>
    </item>
  </channel>
</rss>
