<?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-10-09T07:57:06.814616+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/ghsa-3h2q-j2v4-6w5r</id>
    <title>GHSA-3h2q-j2v4-6w5r — OpenClaw's system.run allowlist approval parsing missed PowerShell encoded-command wrappers</title>
    <updated>2026-10-09T07:57:06.831622+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` shell-wrapper detection did not recognize PowerShell `-EncodedCommand` forms as inline-command wrappers.</p>
<p>In `allowlist` mode, a caller with access to `system.run` could invoke `pwsh` or `powershell` using `-EncodedCommand`, `-enc`, or `-e`, and the request would fall back to plain argv analysis instead of the normal shell-wrapper approval path. This could allow a PowerShell inline payload to execute without the approval step that equivalent `-Command` invocations would require.</p>
<p>Latest published npm version: `2026.3.2`</p>
<p>Fixed on `main` on March 7, 2026 in `1d1757b16f48f1a93cd16ab0ad7e2c3c63ce727d` by recognizing PowerShell encoded-command aliases during shell-wrapper parsing, so allowlist mode continues to require approval for those payloads. Normal approved PowerShell wrapper flows continue 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>- `1d1757b16f48f1a93cd16ab0ad7e2c3c63ce727d`</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-3h2q-j2v4-6w5r"/>
  </entry>
</feed>
