Security readout for executives and security teams
Plain-English summary
OpenClaw’s Microsoft Teams plugin could trust too many people when a route allowlist was configured with an empty sender group field. In that setup, any sender in the matched team or channel could trigger replies, even if the organization expected tighter sender authorization.
Executive priority
Treat this as a targeted configuration and patching priority, not a broad emergency. Prioritize quickly where OpenClaw connects to sensitive Teams channels or where unauthorized replies could disclose internal information.
Technical view
CVE-2026-34506 is a CWE-863 authorization bypass in OpenClaw before 2026.3.8. When a team/channel route allowlist has an empty groupAllowFrom value, the handler synthesizes wildcard sender authorization. CVSS 3.1 is 4.3, with network attack vector, low complexity, low privileges, no user interaction, and limited confidentiality impact.
Likely exposure
Exposure is likely limited to OpenClaw deployments before 2026.3.8 using the Microsoft Teams plugin with route allowlists configured for teams or channels and an empty groupAllowFrom parameter.
Exploitation context
The source bundle does not cite active exploitation, and the CVE is not marked KEV. Exploitation appears to require an unauthorized but authenticated sender in the matched Teams team or channel, based on the CVSS low-privilege requirement.
Researcher notes
The key behavior is authorization synthesis from an empty groupAllowFrom field in a matched team/channel route. Evidence supports confidentiality impact only, with no sourced integrity or availability impact and no sourced public exploitation details.
Mitigation direction
- Upgrade OpenClaw to 2026.3.8 or later.
- Review Microsoft Teams plugin route allowlists for empty groupAllowFrom values.
- Define explicit sender groups for allowlisted Teams routes.
- Check vendor advisory and patch notes for any additional guidance.
- Monitor Teams bot replies for unexpected senders or channels.
Validation and detection
- Inventory OpenClaw versions across production and staging.
- Identify deployments using the Microsoft Teams plugin.
- Inspect route allowlist configurations for empty groupAllowFrom fields.
- Confirm allowlisted routes require explicit sender authorization.
- Review logs for replies triggered by unexpected Teams senders.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-863: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-34506 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N2.81.4VulnCheckCVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
2.3LowVector: 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
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- GitHub Security Advisory (GHSA-g7cr-9h7q-4qxq)CVE reference, VulnCheck · vendor-advisory
- Patch CommitCVE reference, VulnCheck · patch
- VulnCheck Advisory: OpenClaw < 2026.3.8 - Sender Allowlist Bypass in Microsoft Teams Plugin via Route Allowlist ConfigurationCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Incorrect Authorization
Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.