<?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-28T12:06:43.049324+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-41392</id>
    <title>CVE-2026-41392 — OpenClaw &lt; 2026.3.31 - Exec Allowlist Bypass via Shell Init-File Options</title>
    <updated>2026-09-28T12:06:43.805004+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> OpenClaw</p>
<p>OpenClaw before 2026.3.31 contains an exec allowlist bypass vulnerability allowing attackers to inherit allowlist trust via shell init-file wrapper invocations. Attackers can exploit shell options like --rcfile, --init-file, and --startup-file to load attacker-chosen initialization files while bypassing exec allowlist matching restrictions.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-41392"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-wpc6-37g7-8q4w</id>
    <title>GHSA-wpc6-37g7-8q4w — OpenClaw: Shell init-file options could satisfy exec allowlist script matching</title>
    <updated>2026-09-28T12:06:43.805363+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: openclaw</p>
<p>## Summary</p>
<p>Before OpenClaw 2026.3.31, exec allowlist matching could treat shell init-file wrapper invocations as if the approved script itself were being executed. Shell options such as `--rcfile`, `--init-file`, and `--startup-file` could therefore inherit allowlist trust from a matched script path even though the shell loaded attacker-chosen initialization first.</p>
<p>## Impact</p>
<p>This issue only applied when exec allowlist or allow-always behavior was enabled and the attacker could steer a shell-wrapper command shape that used init-file options. The result was a narrower allowlist bypass, not generic arbitrary command execution from an untrusted boundary.</p>
<p>## Affected Packages / Versions</p>
<p>- Package: `openclaw` (npm)
- Affected versions: `&lt; 2026.3.31`
- Patched versions: `&gt;= 2026.3.31`
- Latest published npm version: `2026.4.1`</p>
<p>## Fix Commit(s)</p>
<p>- `0c8375424620e12777ef24c162eedc7e9fcfd7e3` — reject shell init-file script matches</p>
<p>## Release Process Note</p>
<p>The fix shipped in OpenClaw `2026.3.31` on March 31, 2026. The current published npm release `2026.4.1` from April 1, 2026 also contains the fix.</p>
<p>Thanks @cyjhhh for reporting.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-wpc6-37g7-8q4w"/>
  </entry>
</feed>
