CVE-2026-100550: OpenClaw before 2026.8.1 Authentication Bypass via Access Group
OpenClaw (npm package 'openclaw') before 2026.8.1 contains an access-control bypass in the Microsoft Teams integration. When groupPolicy is set to allowlist, a missing or unsupported configured access group produces a denied group-resolution result that is not rejected by the final message-admission check, so a Teams member who is not on the allowlist can still trigger the configured agent despite the administrator's group boundary. The impact depends on the conversations, tools, and data available to that agent. The issue is fixed in version 2026.8.1.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
npm/openclawto a version that resolves this vulnerability.Fixed in 2026.8.1
Event History
Frequently Asked Questions
Which deployments are affected by this bypass?
The issue affects OpenClaw deployments using the Microsoft Teams integration with groupPolicy set to allowlist, where a configured access group is missing or unsupported. Deployments not using that policy condition are not described as affected.
What does an attacker need to exploit it?
An attacker needs to be a Microsoft Teams member able to send messages to the configured agent. They do not need to belong to the administrator's intended allowlisted access group when the group-resolution condition is triggered.
What is the immediate mitigation if upgrading is not possible?
Remove or correct missing and unsupported configured access groups, and avoid relying on the affected allowlist group boundary for message admission. Restrict the agent's available conversations, tools, and data because those determine the resulting impact.
How can administrators determine whether they may be exposed?
Review the OpenClaw version and Microsoft Teams integration configuration. Versions before 2026.8.1 should be reviewed for groupPolicy set to allowlist and configured access groups that are missing or unsupported.