Description
OpenClaw before 2026.3.8 contains a sender allowlist bypass vulnerability in its Microsoft Teams plugin that allows unauthorized senders to bypass intended authorization checks. When a team/channel route allowlist is configured with an empty groupAllowFrom parameter, the message handler synthesizes wildcard sender authorization, permitting any sender in the matched team/channel to trigger replies in allowlisted Teams routes.
Published: 2026-03-31
Score: 2.3 Low
EPSS: < 1% Very Low
KEV: No
Impact: Unauthorized sender access via allowlist bypass
Action: Patch
AI Analysis

Impact

OpenClaw versions prior to 2026.3.8 contain a flaw in the Microsoft Teams plug‑in that allows a sender allowlist to be bypassed. When a team or channel route allowlist is configured with an empty groupAllowFrom field, the message handler creates a wildcard sender authorization. This enables any sender belonging to the matched team/channel to trigger bot replies in allowlisted Teams routes, effectively lifting the intended authorization controls. The weakness is a classic authorization bypass (CWE-863). The consequence is that unauthorized users can gain access to restricted bot interactions, potentially leaking sensitive information or disrupting team workflows. The impact is limited to users who can send messages within the affected Teams channels but could be significant if those channels contain confidential data.

Affected Systems

The vulnerability affects the OpenClaw application (OpenClaw OpenClaw) on all installations using a Microsoft Teams plug‑in. Versions prior to 2026.3.8 are impacted; all later releases are considered fixed.

Risk and Exploitability

The CVSS score is 2.3, indicating a low severity. No EPSS score is available and the issue is not listed in CISA's KEV catalog. The attack requires the ability to send messages in a Microsoft Teams channel that is routed by the OpenClaw plug‑in. The likely attack vector is a user‑initiated message in an improperly configured Teams channel; therefore the exploit is feasible with standard user privileges in the target environment. While the risk is low, the potential for data exposure or unauthorized bot interaction warrants attention.

Generated by OpenCVE AI on March 31, 2026 at 12:22 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade OpenClaw to version 2026.3.8 or later

Generated by OpenCVE AI on March 31, 2026 at 12:22 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 31 Mar 2026 18:15:00 +0000

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N'}

cvssV3_1

{'score': 4.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N'}


Tue, 31 Mar 2026 14:15:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Tue, 31 Mar 2026 11:45:00 +0000

Type Values Removed Values Added
Description OpenClaw before 2026.3.8 contains a sender allowlist bypass vulnerability in its Microsoft Teams plugin that allows unauthorized senders to bypass intended authorization checks. When a team/channel route allowlist is configured with an empty groupAllowFrom parameter, the message handler synthesizes wildcard sender authorization, permitting any sender in the matched team/channel to trigger replies in allowlisted Teams routes.
Title OpenClaw < 2026.3.8 - Sender Allowlist Bypass in Microsoft Teams Plugin via Route Allowlist Configuration
First Time appeared Openclaw
Openclaw openclaw
Weaknesses CWE-863
CPEs cpe:2.3:a:openclaw:openclaw:*:*:*:*:*:node.js:*:*
Vendors & Products Openclaw
Openclaw openclaw
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N'}

cvssV4_0

{'score': 2.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N'}


Subscriptions

Openclaw Openclaw
cve-icon MITRE

Status: PUBLISHED

Assigner: VulnCheck

Published:

Updated: 2026-03-31T17:58:59.365Z

Reserved: 2026-03-30T13:51:47.549Z

Link: CVE-2026-34509

cve-icon Vulnrichment

Updated: 2026-03-31T13:27:27.601Z

cve-icon NVD

Status : Received

Published: 2026-03-31T12:16:30.840

Modified: 2026-03-31T18:16:57.050

Link: CVE-2026-34509

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-03-31T20:38:53Z

Weaknesses