# GHSA-534w-2vm4-89xr: OpenClaw's Zalo group sender allowlist bypass permits unauthorized GROUP dispatch

> Unauthorized users can bypass group sender allowlists to trigger agent processing in Zalo messaging configurations.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Mar 2026

## What is GHSA-534w-2vm4-89xr?

GHSA-534w-2vm4-89xr is a missing authorization vulnerability in openclaw, published on 3 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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)
`openclaw@2026.2.24` is published on npm and contains the fix commit(s) listed above. This advisory now marks `>= 2026.2.24` as patched.

## Which versions are affected by GHSA-534w-2vm4-89xr?

2 open source packages ship an affected version, including openclaw.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `openclaw` | npm | All versions | 2026.2.24 |
| `openclaw` | npm | All versions | 2026.2.24 |

## How do I fix GHSA-534w-2vm4-89xr?

Upgrade openclaw to 2026.2.24 or later.

## Is GHSA-534w-2vm4-89xr being exploited?

There is no known exploitation of GHSA-534w-2vm4-89xr in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-534w-2vm4-89xr and fix it if it is affected.

What it is: GHSA-534w-2vm4-89xr is a missing authorization vulnerability in openclaw, published on 3 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-534w-2vm4-89xr in the wild and no public exploit code.

Affected packages and fixed versions:
- openclaw (npm): affected all versions; fixed in 2026.2.24
- openclaw (npm): affected all versions; fixed in 2026.2.24

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-534w-2vm4-89xr/ (Markdown: https://insights.sbomify.com/GHSA-534w-2vm4-89xr/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-534w-2vm4-89xr

---
From sbomify Insights: https://insights.sbomify.com/GHSA-534w-2vm4-89xr/
Summaries are generated and may contain mistakes; the official description above is the record.