CVE-2026-34506
OpenClaw's MS Teams sender allowlist bypass when route allowlist is configured and sender allowlist is empty
Description
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.
How to fix CVE-2026-34506
To remediate CVE-2026-34506, upgrade the affected package to a fixed version below.
- —upgrade to 2026.3.8 or later
Is CVE-2026-34506 being exploited?
Low — EPSS is 0.0%, meaning exploitation activity has not been observed at scale.
Affected packages (1)
- from 0, < 2026.3.8
CVSS scores
| Source | Version | Severity | Vector |
|---|---|---|---|
| osv | CVSS 4.0 | — | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N |