<?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-28T14:30:12.450433+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-32979</id>
    <title>CVE-2026-32979 — OpenClaw &lt; 2026.3.11 - Unbound Interpreter and Runtime Commands Bypass in node-host Approval</title>
    <updated>2026-09-28T14:30:12.455396+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.11 contains an approval integrity vulnerability allowing attackers to execute rewritten local code by modifying scripts between approval and execution when exact file binding cannot occur. Remote attackers can change approved local scripts before execution to achieve unintended code execution as the OpenClaw runtime user.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-32979"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-xf99-j42q-5w5p</id>
    <title>GHSA-xf99-j42q-5w5p — OpenClaw: Unbound interpreter and runtime commands could bypass node-host approval integrity</title>
    <updated>2026-09-28T14:30:12.455825+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: openclaw</p>
<p>## Summary
In affected versions of `openclaw`, node-host `system.run` approvals could still execute rewritten local code for interpreter and runtime commands when OpenClaw could not bind exactly one concrete local file operand during approval planning.</p>
<p>## Impact
Deployments using node-host `system.run` approval mode could approve a benign local script and then execute different local code if that script changed before execution. This can lead to unintended local code execution as the OpenClaw runtime user.</p>
<p>## Affected Packages and Versions
- Package: `openclaw` (npm)
- Affected versions: `&lt;= 2026.3.8`
- Fixed in: `2026.3.11`</p>
<p>## Technical Details
The approval flow treated some interpreter and runtime forms as approval-backed even when it could not honestly bind a single direct local script file. That left residual approval-integrity gaps for runtime forms outside the directly bound file set.</p>
<p>## Fix
OpenClaw now fails closed for approval-backed interpreter and runtime commands unless it can bind exactly one concrete local file operand, and it extends best-effort direct-file binding for additional runtime forms. The fix shipped in `openclaw@2026.3.11`.</p>
<p>## Workarounds
Upgrade to `2026.3.11` or later.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-xf99-j42q-5w5p"/>
  </entry>
</feed>
