<?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-29T07:33:15.952876+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/brew-openclaw-cli-cve-2026-41368</id>
    <title>BREW-openclaw-cli-CVE-2026-41368 — OpenClaw safeBins jq `$ENV` filter bypass allows environment variable disclosure</title>
    <updated>2026-09-29T07:33:15.955580+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Homebrew: openclaw-cli</p>
<p>## Summary</p>
<p>The jq safe-bin policy blocked explicit `env` usage but still allowed jq programs that accessed environment data through `$ENV`.</p>
<p>## Impact</p>
<p>An operator-approved safe-bin jq command could disclose environment variables that the safe-bin policy was supposed to keep out of scope.</p>
<p>## Affected Component</p>
<p>`src/infra/exec-safe-bin-semantics.ts`</p>
<p>## Fixed Versions</p>
<p>- Affected: `&lt;= 2026.3.24`
- Patched: `&gt;= 2026.3.28`
- Latest stable `2026.3.28` contains the fix.</p>
<p>## Fix</p>
<p>Fixed by commit `78e2f3d66d` (`Exec: tighten jq safe-bin env checks`).</p>
<p>Thanks @nicky-cc  of Tencent zhuque Lab ([https://github.com/Tencent/AI-Infra-Guard](https://github.com/Tencent/AI-Infra-Guard)) for reporting.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/brew-openclaw-cli-cve-2026-41368"/>
  </entry>
</feed>
