CVE-2026-34506: OpenClaw's MS Teams sender allowlist bypass when route allowlist is configured and sender allowlist is empty
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.
Published Mar 12, 2026 · Updated Apr 6, 2026
Affected packages
openclaw
- Ecosystem
- npm
- Affected
- <= 2026.3.7
- Fixed in
- 2026.3.8
- Check
npm ls openclaw
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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.8published on March 9, 2026. - Verified
npm view openclaw versionresolves to2026.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.8tree.
Thanks @zpbrent for reporting.
Credited to zpbrent.
References
- https://github.com/openclaw/openclaw/security/advisories/GHSA-g7cr-9h7q-4qxq
- https://github.com/openclaw/openclaw/commit/88aee9161e0e6d32e810a25711e32a808a1777b2
- https://nvd.nist.gov/vuln/detail/CVE-2026-34506
- https://www.vulncheck.com/advisories/openclaw-sender-allowlist-bypass-in-microsoft-teams-plugin-via-route-allowlist-configuration
- https://github.com/advisories/GHSA-g7cr-9h7q-4qxq
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. No analysis has been written for this entry yet. Methodology
More OpenClaw vulnerabilities
All OpenClaw entriesCVE-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, 2026CVE-2026-53812
OpenClaw's browser act interactions could bypass private-network navigation checks
medium7.7Jul 2, 2026
