CVE-2026-34506
Sender Allowlist Bypass in OpenClaw Microsoft Teams Plugin
Publication date: 2026-03-31
Last updated on: 2026-04-01
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| openclaw | openclaw | to 2026.3.8 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-863 | The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-34506 is a sender allowlist bypass vulnerability in the Microsoft Teams plugin of OpenClaw versions before 2026.3.8.
When a team or channel route allowlist is configured with an empty sender allowlist parameter (groupAllowFrom), the message handler incorrectly creates a wildcard sender authorization. This means that any sender within the matched team or channel can bypass the intended authorization checks and trigger replies in allowlisted Teams routes.
The root cause is that the authorization logic did not strictly enforce sender allowlists when a route allowlist was present, allowing unauthorized senders to gain access by being part of the route allowlist.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided information does not explicitly discuss the impact of CVE-2026-34506 on compliance with common standards and regulations such as GDPR or HIPAA.
How can this vulnerability impact me? :
This vulnerability can allow unauthorized senders within a matched Microsoft Teams team or channel to bypass intended authorization checks.
As a result, unauthorized users could trigger replies in allowlisted Teams routes, potentially leading to unintended information disclosure or interaction within Teams channels that were expected to be restricted.
Although it does not affect default unauthenticated access, it weakens the group authorization boundaries, allowing broader access than intended.
What immediate steps should I take to mitigate this vulnerability?
To mitigate the vulnerability CVE-2026-34506, you should upgrade OpenClaw to version 2026.3.8 or later, where the issue has been fixed.
The fix enforces sender allowlists strictly alongside route allowlists in the Microsoft Teams plugin, preventing unauthorized senders from bypassing authorization checks.
- Update OpenClaw to version 2026.3.8 or newer.
- Review your Microsoft Teams plugin configuration to ensure that sender allowlists (groupAllowFrom) are properly set and not left empty.
- Verify that your team/channel route allowlists do not rely on empty sender allowlists, which could allow wildcard sender authorization.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability involves a sender allowlist bypass in OpenClaw's Microsoft Teams plugin when a route allowlist is configured with an empty sender allowlist (groupAllowFrom). Detection involves verifying the configuration of OpenClaw's Microsoft Teams plugin, specifically checking if any team or channel route allowlist is set with an empty groupAllowFrom parameter.
To detect this vulnerability on your system, you should:
- Inspect the OpenClaw Microsoft Teams plugin configuration files or settings for route allowlists that have an empty or missing groupAllowFrom parameter.
- Check the version of OpenClaw installed; versions prior to 2026.3.8 are vulnerable.
While no specific detection commands are provided in the resources, general commands to check the version and configuration might include:
- Check OpenClaw version: `openclaw --version` or check the installed package version via npm: `npm list openclaw`.
- Review the Microsoft Teams plugin configuration files for route allowlist settings, for example by searching for `groupAllowFrom` in configuration files: `grep -r 'groupAllowFrom' /path/to/openclaw/config`.
- Audit logs or message handler behavior to identify if unauthorized senders are able to trigger replies in allowlisted Teams routes, which may indicate exploitation.
For precise detection, reviewing the authorization logic or applying the patch from version 2026.3.8 is recommended to prevent this bypass.