<?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-10-02T04:50:16.365770+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-32005</id>
    <title>CVE-2026-32005 — OpenClaw &lt; 2026.2.25 - Authorization Bypass in Interactive Callbacks via Sender Check Skip</title>
    <updated>2026-10-02T04:50:16.370065+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.2.25 fail to enforce sender authorization checks for interactive callbacks including block_action, view_submission, and view_closed in shared workspace deployments. Unauthorized workspace members can bypass allowFrom restrictions and channel user allowlists to enqueue system-event text into active sessions.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-32005"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-x2ff-j5c2-ggpr</id>
    <title>GHSA-x2ff-j5c2-ggpr — OpenClaw: Slack interactive callbacks could skip configured sender checks in some shared-workspace flows</title>
    <updated>2026-10-02T04:50:16.370307+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: openclaw</p>
<p>## Impact</p>
<p>In shared Slack workspace deployments that rely on sender restrictions (`allowFrom`, DM policy, or channel user allowlists), some interactive callbacks (`block_action`, `view_submission`, `view_closed`) could be accepted before full sender authorization checks.</p>
<p>In that scenario, an unauthorized workspace member could enqueue system-event text into an active session. This issue did not provide unauthenticated access, cross-gateway isolation bypass, or host-level privilege escalation by itself.</p>
<p>## Affected Packages / Versions</p>
<p>- Package: `openclaw` (npm)
- Vulnerable versions: `&lt;= 2026.2.24`
- Patched version: `2026.2.25` (planned next npm release)</p>
<p>## Fix Commit(s)</p>
<p>- `ce8c67c314b93f570f53c2a9abc124e1e3a54715`</p>
<p>## Release Process Note</p>
<p>`patched_versions` is pre-set to the release (`2026.2.25`). Advisory published with npm release `2026.2.25`.</p>
<p>## Trust Model Scope Note</p>
<p>OpenClaw does not support adversarial multi-user isolation on a single shared gateway instance. The supported model is one trust boundary per gateway (separate gateways/hosts for mutually untrusted users). See: https://docs.openclaw.ai/gateway/security</p>
<p>OpenClaw thanks @tdjackey for reporting.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-x2ff-j5c2-ggpr"/>
  </entry>
</feed>
