openclaw MS Teams up to 2026.5.26 Outbound Request information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 1.40+ |
Summary
A vulnerability classified as problematic was found in openclaw MS Teams up to 2026.5.26. Affected is an unknown function of the component Outbound Request Handler. Executing a manipulation can lead to information disclosure. This vulnerability appears as CVE-2026-62213. The attack may be performed from remote. There is no available exploit.
Details
A vulnerability was found in openclaw MS Teams up to 2026.5.26. It has been declared as problematic. This vulnerability affects an unknown function of the component Outbound Request Handler. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality. CVE summarizes:
OpenClaw versions before 2026.5.27 contain a token leakage vulnerability in MS Teams outbound requests that allows lower-trust callers to expose Bot Framework tokens. Attackers can access configured input paths to retrieve credentials that should remain within the trusted boundary.
The advisory is shared for download at github.com. This vulnerability was named CVE-2026-62213 since 07/13/2026. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1592.
Upgrading to version 2026.5.27 eliminates this vulnerability.
Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
Version
- 2026.5.0
- 2026.5.1
- 2026.5.2
- 2026.5.3
- 2026.5.4
- 2026.5.5
- 2026.5.6
- 2026.5.7
- 2026.5.8
- 2026.5.9
- 2026.5.10
- 2026.5.11
- 2026.5.12
- 2026.5.13
- 2026.5.14
- 2026.5.15
- 2026.5.16
- 2026.5.17
- 2026.5.18
- 2026.5.19
- 2026.5.20
- 2026.5.21
- 2026.5.22
- 2026.5.23
- 2026.5.24
- 2026.5.25
- 2026.5.26
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
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: Information disclosureCWE: CWE-200 / CWE-284 / 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: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Upgrade: MS Teams 2026.5.27
Timeline
07/13/2026 CVE reserved07/17/2026 Advisory disclosed
07/17/2026 VulDB entry created
07/17/2026 VulDB entry last update
Sources
Advisory: github.comStatus: Confirmed
CVE: CVE-2026-62213 (🔒)
GCVE (CVE): GCVE-0-2026-62213
GCVE (VulDB): GCVE-100-379708
Entry
Created: 07/17/2026 03:00Changes: 07/17/2026 03:00 (54)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.