https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 28 Sep 2026 10:24:23 +0000 https://vulnerability.circl.lu/vuln/cve-2026-27183 <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> <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> https://vulnerability.circl.lu/vuln/cve-2026-27183 https://vulnerability.circl.lu/vuln/ghsa-r6qf-8968-wj9q <p><strong>Affected:</strong> npm: openclaw</p> <p>OpenClaw&#39;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> <p><strong>Affected:</strong> npm: openclaw</p> <p>OpenClaw&#39;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> https://vulnerability.circl.lu/vuln/ghsa-r6qf-8968-wj9q