<?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-12T08:22:35.311803+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/ghsa-534w-2vm4-89xr</id>
    <title>GHSA-534w-2vm4-89xr — OpenClaw's Zalo group sender allowlist bypass permits unauthorized GROUP dispatch</title>
    <updated>2026-10-12T08:22:35.426924+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: openclaw</p>
<p>A missing group-sender authorization check in the Zalo plugin allowed unauthorized `GROUP` messages to enter agent dispatch paths in configurations intended to restrict group traffic.</p>
<p>## Impact
When Zalo group handling was configured with allowlist-style controls, a sender not present in the intended group allowlist could still trigger agent processing through the `GROUP` message path.</p>
<p>## Root Cause
Group access checks were not consistently enforced before dispatch for Zalo `GROUP` messages. The fix adds explicit runtime group-policy evaluation (`groupPolicy`, `groupAllowFrom`, fallback to `allowFrom`) and fail-closed behavior for missing provider config.</p>
<p>## Affected Packages / Versions
- Package: `openclaw` (npm)
- Latest published vulnerable version: `2026.2.23` (as of 2026-02-24)
- Affected range: `&lt;= 2026.2.23`
- Planned patched version: `2026.2.24`</p>
<p>## Fix Commit(s)
- `b4010a0b627025c809c0e5dbdbd4770f3bc59ef8`</p>
<p>OpenClaw thanks @tdjackey for reporting.</p>
<p>### Publication Update (2026-02-25)
`openclaw@2026.2.24` is published on npm and contains the fix commit(s) listed above. This advisory now marks `&gt;= 2026.2.24` as patched.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-534w-2vm4-89xr"/>
  </entry>
</feed>
