OpenClaw up to 2026.6.9 Microsoft Teams Integration groupPolicy privileges management
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.7 | $0-$5k | 0.00+ |
Summary
A vulnerability was found in OpenClaw. It has been classified as critical. Affected is an unknown function of the component Microsoft Teams Integration. Performing a manipulation of the argument groupPolicy results in privileges management. This vulnerability is identified as CVE-2026-100550. The attack can be initiated remotely. There is not any exploit available. Upgrading the affected component is recommended.
Details
A vulnerability was found in OpenClaw. It has been classified as critical. This affects an unknown code block of the component Microsoft Teams Integration. The manipulation of the argument groupPolicy with an unknown input leads to a privileges management vulnerability. CWE is classifying the issue as CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
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.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-100550 since 09/26/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1068 for this issue.
Upgrading to version 2026.8.1 eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
- 0.1.33
- 0.2.39
- 0.5.71
- 0.9.43
- 1.1.0
- 3.0.0
- 2026.1.20
- 2026.1.29
- 2026.1.30
- 2026.2.1
- 2026.2.2
- 2026.2.3
- 2026.2.5
- 2026.2.6
- 2026.2.12
- 2026.2.13
- 2026.2.14
- 2026.2.15
- 2026.2.17
- 2026.2.18
- 2026.2.19
- 2026.2.19-2
- 2026.2.19-beta.1
- 2026.2.21
- 2026.2.21-beta.1
- 2026.2.22
- 2026.2.23
- 2026.2.24
- 2026.2.25
- 2026.2.26
- 2026.3.1
- 2026.3.2
- 2026.3.7
- 2026.3.8
- 2026.3.11
- 2026.3.12
- 2026.3.13
- 2026.3.22
- 2026.3.23
- 2026.3.24
- 2026.3.25
- 2026.3.28
- 2026.3.31
- 2026.4.2
- 2026.4.4
- 2026.4.5
- 2026.4.7
- 2026.4.8
- 2026.4.9
- 2026.4.10
- 2026.4.12
- 2026.4.14
- 2026.4.15
- 2026.4.20
- 2026.4.21
- 2026.4.22
- 2026.4.23
- 2026.4.24
- 2026.4.25
- 2026.4.26
- 2026.4.27
- 2026.4.29
- 2026.5.2
- 2026.5.3
- 2026.5.4
- 2026.5.6
- 2026.5.7
- 2026.5.12
- 2026.5.18
- 2026.5.19
- 2026.5.20
- 2026.5.22
- 2026.5.26
- 2026.5.27
- 2026.5.28
- 2026.6.1
- 2026.6.5
- 2026.6.6
- 2026.6.8
- 2026.6.9
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 5.9VulDB Meta Temp Score: 5.7
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 5.4
CNA Vector (VulnCheck): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Privileges managementCWE: CWE-269 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: OpenClaw 2026.8.1
Timeline
09/26/2026 Advisory disclosed09/26/2026 CVE reserved
09/26/2026 VulDB entry created
09/26/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CVE: CVE-2026-100550 (🔒)
GCVE (CVE): GCVE-0-2026-100550
GCVE (VulDB): GCVE-100-410541
Entry
Created: 09/26/2026 05:02Changes: 09/26/2026 05:02 (77)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.