<?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-30T23:20:17.543371+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-31997</id>
    <title>CVE-2026-31997 — OpenClaw &lt; 2026.3.1 - Executable Rebind via Unbound PATH-token in system.run Approvals</title>
    <updated>2026-09-30T23:20:18.289502+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.1 fail to pin executable identity for non-path-like argv[0] tokens in system.run approvals, allowing post-approval executable rebind attacks. Attackers can modify PATH resolution after approval to execute a different binary than the operator approved, enabling arbitrary command execution.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-31997"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-q399-23r3-hfx4</id>
    <title>GHSA-q399-23r3-hfx4 — OpenClaw: system.run approvals did not bind PATH-token executable identity, enabling post-approval executable rebind</title>
    <updated>2026-09-30T23:20:18.289919+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: openclaw</p>
<p>### Summary
For `host=node` runs, approvals validated command context but did not pin executable identity for non-path-like `argv[0]` tokens (for example `tr`). If PATH resolution changed after approval, execution could run a different binary.</p>
<p>### Impact
A previously approved action could execute a different executable than the operator approved.</p>
<p>### Fix
Node `system.run` approvals now require immutable `systemRunPlan` data, and path-token commands are pinned to canonical executable identity (`realpath`) across approval and execution.</p>
<p>### Affected and Patched Versions
- Affected: `&lt;= 2026.2.26`
- Patched: `2026.3.1`</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-q399-23r3-hfx4"/>
  </entry>
</feed>
