GHSA-534w-2vm4-89xr: OpenClaw's Zalo group sender allowlist bypass permits unauthorized GROUP dispatch
The Zalo plugin in OpenClaw up to 2026.2.23 did not check group senders consistently before dispatch. A sender missing from the intended group allowlist could still start agent processing through a `GROUP` message. Upgrade `openclaw` to 2026.2.24.
Published Mar 3, 2026 · Analysis Oct 31, 2026
What an attacker can do
In Zalo configurations that restrict group traffic with allowlist-style controls, the GROUP message path did not enforce the group access check before the message went to agent dispatch. A person who was not on the group allowlist could therefore post in a group the bot listens to and trigger the agent anyway (CWE-284, CWE-863).
The attacker needs a Zalo account that can reach the group the bot reads. The CVSS 4.0 vector shows network access, low privileges and no user interaction, with low integrity impact. What the attacker gets is the ability to give the agent input that your policy meant to block. Whatever the agent does with group messages, such as answering, running tools or acting on instructions, is open to that sender. Teams that rely on the allowlist as the only barrier between a public group and an agent with tool access should treat this as a real exposure, even though the advisory rates it medium.
Who is affected
The openclaw npm package up to and including 2026.2.23 (the latest vulnerable version on 2026-02-24), with the Zalo plugin enabled and group handling restricted by groupPolicy, groupAllowFrom or allowFrom. Check the version:
npm ls openclaw
openclaw --versionThen review the Zalo section of your config for group allowlist settings.
openclaw
- Ecosystem
- npm
- Affected
- <= 2026.2.23
- Fixed in
- 2026.2.24
- Check
npm ls openclaw
How to fix it
Upgrade to 2026.2.24:
npm install -g [email protected]The fix (commit b4010a0b627025c809c0e5dbdbd4770f3bc59ef8) adds explicit runtime group-policy evaluation using groupPolicy and groupAllowFrom, falling back to allowFrom. It fails closed when the provider config is missing. Version 2026.2.24 was published on npm on 2026-02-25. The sources name no workaround.
How to tell if you were hit
Review agent session history for Zalo GROUP messages from sender IDs that are not in groupAllowFrom or allowFrom. Check whether the agent ran tools or replied in response to those messages. The sources give no fixed log string for this flaw.
Original advisory
From the GitHub Advisory Database (CC BY 4.0).
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.
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.
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.
Affected Packages / Versions
- Package:
openclaw(npm) - Latest published vulnerable version:
2026.2.23(as of 2026-02-24) - Affected range:
<= 2026.2.23 - Planned patched version:
2026.2.24
Fix Commit(s)
b4010a0b627025c809c0e5dbdbd4770f3bc59ef8
OpenClaw thanks @tdjackey for reporting.
Publication Update (2026-02-25)
[email protected] is published on npm and contains the fix commit(s) listed above. This advisory now marks >= 2026.2.24 as patched.
Credited to tdjackey.
Questions
- Which version fixes GHSA-534w-2vm4-89xr?
OpenClaw 2026.2.24, published on npm on 2026-02-25. Version 2026.2.23 and earlier are affected.
- What settings does the fix evaluate?
groupPolicy and groupAllowFrom, with a fallback to allowFrom. If the provider config is missing, group messages are now rejected.
- Are direct messages affected?
The advisory describes only the GROUP message path in the Zalo plugin.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology
More OpenClaw vulnerabilities
All OpenClaw entriesCVE-2026-62197
OpenClaw: Browser CDP discovery could accept blocked WebSocket URLs
medium8.5Oct 21, 2026CVE-2026-35630
OpenClaw: QQBot native approval buttons did not enforce configured approver identity
high8.0Jul 2, 2026CVE-2026-53806
OpenClaw: Combined POSIX shell options could confuse exec revalidation
high8.8Jul 2, 2026CVE-2026-53809
OpenClaw: Embedded runner policy could be confused by provider aliases
medium3.8Jul 2, 2026CVE-2026-53810
OpenClaw's marketplace runtime extension metadata could point at unscanned payloads
high8.8Jul 2, 2026CVE-2026-53811
OpenClaw: Matrix allowFrom could bind to mutable display names
high8.8Jul 2, 2026
