GHSA-g7cr-9h7q-4qxq OpenClaw's MS Teams sender allowlist bypass when route allowlist is configured and sender allowlist is empty

• npm openclaw: < 2026.3.8 → fixed in 2026.3.8

OpenClaw's Microsoft Teams plugin widened group sender authorization when a team/channel route allowlist was configured but `groupAllowFrom` was empty. Before the fix, a matching route allowlist entry could cause the message handler to synthesize wildcard sender authorization for that route, allowing any sender in the matched team/channel to bypass the intended `groupPolicy: "allowlist"` sender check. This does not affect default unauthenticated access, but it does weaken a documented Teams group authorization boundary and can allow unauthorized group senders to trigger replies in allowlisted Teams routes. Affected Packages / Versions • Package: `openclaw` (npm) • Latest published vulnerable version: `2026.3.7` • Affected range: `<= 2026.3.7` • Fixed in released version: `2026.3.8` Fix Commit(s) • `88aee9161e0e6d32e810a25711e32a808a1777b2` Release Verification • Verified fixed in GitHub release `v2026.3.8` published on March 9, 2026. • Verified `npm view openclaw version` resolves to `2026.3.8`. • Verified the release contains the regression test covering the Teams route-allowlist sender-bypass case and that the test passes against the `v2026.3.8` tree. Thanks @zpbrent for reporting.