Sender Allowlist Bypass in OpenClaw Microsoft Teams Plugin

Publication date: 2026-03-31

Last updated on: 2026-04-01

Assigner: VulnCheck

Description

Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-03-31

Last Modified

2026-04-01

Generated

2026-07-06

AI Q&A

2026-03-31

EPSS Evaluated

2026-04-01

NVD

CVE-2026-34509

EUVD

EUVD-2026-17395

Affected Vendors & Products

Vendor	Product	Version / Range
openclaw	openclaw	to 2026.3.8 (exc)

Helpful Resources

Exploitability

CWE

KEV

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

Executive Summary

This vulnerability exists in OpenClaw versions before 2026.3.8, specifically in its Microsoft Teams plugin. It is a sender allowlist bypass issue where unauthorized senders can bypass the intended authorization checks. When a team or channel route allowlist is configured with an empty groupAllowFrom parameter, the message handler incorrectly synthesizes a wildcard sender authorization. This means that any sender in the matched team or channel can trigger replies in allowlisted Teams routes, even if they are not explicitly authorized.

Impact Analysis

The impact of this vulnerability is that unauthorized users can send messages that trigger replies in Microsoft Teams routes that are supposed to be restricted. This could lead to unauthorized communication or actions within Teams channels or teams that rely on OpenClaw's allowlist for sender authorization. Essentially, it undermines the security controls intended to limit who can interact with certain Teams routes.

Hi! I’m here to help you understand CVE-2026-34509. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70