<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 02 Oct 2026 17:13:19 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-32022 — OpenClaw &lt; 2026.2.21 - Arbitrary File Read via grep -e Flag Policy Bypass</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-32022</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; OpenClaw&lt;/p&gt;
&lt;p&gt;OpenClaw versions prior to 2026.2.21 contain a stdin-only policy bypass vulnerability in the grep tool within tools.exec.safeBins that allows attackers to read arbitrary files by supplying a pattern via the -e flag parameter. Attackers can include a positional filename operand to bypass file access restrictions and read sensitive files.env from the working directory.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; OpenClaw&lt;/p&gt;
&lt;p&gt;OpenClaw versions prior to 2026.2.21 contain a stdin-only policy bypass vulnerability in the grep tool within tools.exec.safeBins that allows attackers to read arbitrary files by supplying a pattern via the -e flag parameter. Attackers can include a positional filename operand to bypass file access restrictions and read sensitive files.env from the working directory.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-32022</guid>
    </item>
    <item>
      <title>GHSA-3xfw-4pmr-4xc5 — OpenClaw safeBins grep -e File Read Bypass (stdin-only policy bypass)</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-3xfw-4pmr-4xc5</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: openclaw&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;OpenClaw `tools.exec.safeBins` had a stdin-only policy bypass for `grep`.
If pattern input was supplied through `-e` / `--regexp`, the validator consumed the pattern as a flag value and still allowed one positional operand. That positional could be a bare filename like `.env`.&lt;/p&gt;
&lt;p&gt;### Affected Packages / Versions&lt;/p&gt;
&lt;p&gt;- Package: `openclaw` (npm)
- Latest published vulnerable version: `2026.2.19-2`
- Structured vulnerable range: `&amp;lt;= 2026.2.19-2`
- Planned fixed range for next release: `&amp;gt;= 2026.2.21`&lt;/p&gt;
&lt;p&gt;### Exploit Preconditions&lt;/p&gt;
&lt;p&gt;- `tools.exec.safeBins` must include `grep` (this is opt-in; `grep` is not in the default safe-bin list).
- An actor must be able to invoke exec tooling under that profile.&lt;/p&gt;
&lt;p&gt;### Technical Details&lt;/p&gt;
&lt;p&gt;`src/infra/exec-safe-bin-policy.ts` configured `grep` with `maxPositional: 1` and allowed `-e` / `--regexp` value flags.
Because `-e` consumes the pattern in flag-value position, the remaining positional budget could be used for a file operand.
Example accepted input in vulnerable builds:&lt;/p&gt;
&lt;p&gt;```bash
grep -e SECRET .env
```&lt;/p&gt;
&lt;p&gt;That violated the intended stdin-only guarantee for safe bins.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;With `grep` opt-in enabled, callers could read bare-relative files from the working directory (for example `.env`, `credentials.txt`) in flows expected to be stdin-only.&lt;/p&gt;
&lt;p&gt;### Severity Rationale&lt;/p&gt;
&lt;p&gt;CVSS v3.1 is set to:
`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N` (5.3, Medium)&lt;/p&gt;
&lt;p&gt;`AC:H` is used because exploitation depends on a non-default configuration (`grep` mus…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: openclaw&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;OpenClaw `tools.exec.safeBins` had a stdin-only policy bypass for `grep`.
If pattern input was supplied through `-e` / `--regexp`, the validator consumed the pattern as a flag value and still allowed one positional operand. That positional could be a bare filename like `.env`.&lt;/p&gt;
&lt;p&gt;### Affected Packages / Versions&lt;/p&gt;
&lt;p&gt;- Package: `openclaw` (npm)
- Latest published vulnerable version: `2026.2.19-2`
- Structured vulnerable range: `&amp;lt;= 2026.2.19-2`
- Planned fixed range for next release: `&amp;gt;= 2026.2.21`&lt;/p&gt;
&lt;p&gt;### Exploit Preconditions&lt;/p&gt;
&lt;p&gt;- `tools.exec.safeBins` must include `grep` (this is opt-in; `grep` is not in the default safe-bin list).
- An actor must be able to invoke exec tooling under that profile.&lt;/p&gt;
&lt;p&gt;### Technical Details&lt;/p&gt;
&lt;p&gt;`src/infra/exec-safe-bin-policy.ts` configured `grep` with `maxPositional: 1` and allowed `-e` / `--regexp` value flags.
Because `-e` consumes the pattern in flag-value position, the remaining positional budget could be used for a file operand.
Example accepted input in vulnerable builds:&lt;/p&gt;
&lt;p&gt;```bash
grep -e SECRET .env
```&lt;/p&gt;
&lt;p&gt;That violated the intended stdin-only guarantee for safe bins.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;With `grep` opt-in enabled, callers could read bare-relative files from the working directory (for example `.env`, `credentials.txt`) in flows expected to be stdin-only.&lt;/p&gt;
&lt;p&gt;### Severity Rationale&lt;/p&gt;
&lt;p&gt;CVSS v3.1 is set to:
`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N` (5.3, Medium)&lt;/p&gt;
&lt;p&gt;`AC:H` is used because exploitation depends on a non-default configuration (`grep` mus…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-3xfw-4pmr-4xc5</guid>
    </item>
  </channel>
</rss>
