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.
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.
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.
openclaw (npm)2026.2.23 (as of 2026-02-24)<= 2026.2.232026.2.24b4010a0b627025c809c0e5dbdbd4770f3bc59ef8OpenClaw thanks @tdjackey for reporting.
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.
{
"github_reviewed_at": "2026-03-03T23:18:26Z",
"github_reviewed": true,
"cwe_ids": [
"CWE-284",
"CWE-863"
],
"nvd_published_at": null,
"severity": "MODERATE"
}