Is there a patch available for CVE-2026-62213?

Yes, a patch is available for CVE-2026-62213. Update the affected software to the latest version immediately.

OpenClaw CVE-2026-62213

Q: What is the CVSS score of CVE-2026-62213?

CVE-2026-62213 has a CVSS 4.0 base score of 6.0 (Medium). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.3%.

EUVD-2026-45101 MEDIUM

Insufficiently Protected Credentials (CWE-522)

2026-07-17 VulnCheck

GHSA-q8cf-gmjr-64qh

Information Disclosure Openclaw Msteams

6.0

CVSS 4.0 · Vendor: VulnCheck

Severity by source

Vendor (VulnCheck) PRIMARY

6.0 MEDIUM

CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

vuln.today AI

5.3 MEDIUM

Network-reachable with low privileges, but the CVSS 4.0 AT:P condition maps to AC:H in 3.1; no integrity or availability impact applies.

3.1 AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N

4.0 AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

Patch available

Jul 17, 2026 - 02:32 EUVD

Analysis Generated

Jul 17, 2026 - 01:06 vuln.today

DescriptionCVE.org

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.

AnalysisAI

Token leakage in OpenClaw's MS Teams integration (versions before 2026.5.27) allows lower-trust authenticated callers to retrieve Bot Framework tokens that should remain within the application's trusted boundary. Attackers exploit access to configured input paths involved in outbound MS Teams requests to harvest bearer tokens, which can then be used to authenticate to downstream Microsoft Bot Framework or Teams services as the compromised bot identity. No public exploit code exists and this vulnerability is not listed in CISA KEV, but the high confidentiality impact (VC:H) and credential theft potential make patching a priority for any organization running this integration.

Technical ContextAI

The affected component is the OpenClaw MS Teams integration module, identified by CPE cpe:2.3:a:openclaw:msteams:*:*:*:*:*:*:*:*. Bot Framework tokens are OAuth bearer tokens issued by Microsoft to authenticate bots against the Bot Framework service and MS Teams APIs - exposure of these tokens allows impersonation of the bot and unauthorized access to any service the bot identity is authorized to reach. The root cause is CWE-522 (Insufficiently Protected Credentials): the application fails to adequately protect these tokens from lower-trust callers when processing outbound MS Teams requests, making them accessible via configured input paths. The CVSS 4.0 AT:P metric (Attack Requirements: Present) indicates that a specific environmental or configuration condition must be met beyond simple authentication, consistent with the description's reference to 'configured input paths' as the access vector.

RemediationAI

Upgrade OpenClaw to version 2026.5.27 or later, which is the vendor-confirmed fixed release per the GitHub advisory at https://github.com/openclaw/openclaw/security/advisories/GHSA-v54h-q2vx-vgg4. After upgrading, rotate any Bot Framework tokens that may have been exposed - invalidating compromised credentials prevents post-exploitation use even if tokens were already harvested. If immediate upgrade is not feasible, restrict access to the configured input paths involved in MS Teams outbound request handling to fully-trusted callers only, using network-layer ACLs or application-level authorization controls; this reduces the lower-trust caller attack surface but does not eliminate the underlying credential protection flaw. Additional context from VulnCheck is available at https://www.vulncheck.com/advisories/openclaw-token-leakage-via-ms-teams-outbound-requests.