<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-28T10:24:24.543397+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-27183</id>
    <title>CVE-2026-27183 — OpenClaw &lt; 2026.3.7 - Shell Approval Gating Bypass via Dispatch Wrapper Depth Mismatch</title>
    <updated>2026-09-28T10:24:24.546133+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> OpenClaw</p>
<p>OpenClaw versions prior to 2026.3.7 contain a shell approval gating bypass vulnerability in system.run dispatch-wrapper handling that allows attackers to skip shell wrapper approval requirements. The approval classifier and execution planner apply different depth-boundary rules, permitting exactly four transparent dispatch wrappers like repeated env invocations before /bin/sh -c to bypass security=allowlist approval gating by misaligning classification with execution planning.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-27183"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-r6qf-8968-wj9q</id>
    <title>GHSA-r6qf-8968-wj9q — OpenClaw: system.run wrapper-depth boundary could skip shell approval gating</title>
    <updated>2026-09-28T10:24:24.546225+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: openclaw</p>
<p>OpenClaw's `system.run` dispatch-wrapper handling applied different depth-boundary rules to shell-wrapper approval detection and execution planning.</p>
<p>With exactly four transparent dispatch wrappers such as repeated `env` invocations before `/bin/sh -c`, the approval classifier could stop treating the command as a shell wrapper at the depth boundary while execution planning still unwrapped through to the shell payload. In `security=allowlist` mode, that mismatch could skip the expected approval-required path for the shell wrapper invocation.</p>
<p>Latest published npm version: `2026.3.2`</p>
<p>Fixed on `main` on March 7, 2026 in `2fc95a7cfc1eb9306356510b0251b6d51fb1c0b0` by keeping shell-wrapper classification active at the configured dispatch depth boundary and only failing closed beyond that boundary. This aligns approval gating with the execution plan. Legitimate shallow dispatch-wrapper usage continues to work.</p>
<p>## Affected Packages / Versions</p>
<p>- Package: `openclaw` (npm)
- Affected versions: `&lt;= 2026.3.2`
- Patched version: `&gt;= 2026.3.7`</p>
<p>## Fix Commit(s)</p>
<p>- `2fc95a7cfc1eb9306356510b0251b6d51fb1c0b0`</p>
<p>## Release Process Note</p>
<p>npm `2026.3.7` was published on March 8, 2026. This advisory is fixed in the released package.</p>
<p>Thanks @tdjackey for reporting.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-r6qf-8968-wj9q"/>
  </entry>
</feed>
