<?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-30T04:44:17.372916+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-32035</id>
    <title>CVE-2026-32035 — OpenClaw &lt; 2026.3.2 - Missing Owner Flag Validation in Discord Voice Transcript Handler</title>
    <updated>2026-09-30T04:44:17.375058+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.2 fail to pass the senderIsOwner flag when processing Discord voice transcripts in agentCommand, causing the flag to default to true. Non-owner voice participants can exploit this omission to access owner-only tools including gateway and cron functionality in mixed-trust channels.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-32035"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-wpg9-4g4v-f9rc</id>
    <title>GHSA-wpg9-4g4v-f9rc — OpenClaw: Discord voice transcript owner-flag omission could expose owner-only tools in mixed-trust channels</title>
    <updated>2026-09-30T04:44:17.375167+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: openclaw</p>
<p>### Summary
In `openclaw@2026.3.1`, the Discord voice transcript path called `agentCommand(...)` without `senderIsOwner`, and `agentCommand` defaults missing `senderIsOwner` to `true`.</p>
<p>This could allow a non-owner voice participant in the same channel to reach owner-only tool surfaces (`gateway`, `cron`) during voice transcript turns.</p>
<p>### Security model note
OpenClaw’s documented trust model is a **personal assistant** model (one trusted operator), not an adversarial multi-user boundary.</p>
<p>- OpenClaw does **not** treat one shared gateway/chat surface as a hardened per-user auth boundary.
- Mixed-trust deployments (mutually untrusted users sharing one gateway/channel) are outside recommended deployment boundaries.</p>
<p>This report is treated as a valid hardening/authorization bug because owner-only tool policy should still be applied consistently across chat-driven turns, including Discord voice transcript ingress.</p>
<p>### Details
Relevant path:
1. Voice transcript run omitted `senderIsOwner` in Discord voice manager.
2. Missing `senderIsOwner` defaulted to `true` in `agentCommand`.
3. Owner-only tool policy is keyed on `senderIsOwner`.
4. `gateway` and `cron` are owner-only tools.</p>
<p>### Impact
- Affects deployments where Discord voice is enabled and the bot is present in channels with non-owner participants.
- No gateway-auth boundary bypass was required.
- Practical risk depends strongly on whether the deployment is single-trust (recommended) or mixed-trust (not recommended).</p>
<p>###…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-wpg9-4g4v-f9rc"/>
  </entry>
</feed>
