Token disclosure via untrusted outbound service URLs
Published Jul 17, 2026 · Updated Oct 8, 2026
Token leakage in @openclaw/msteams before 2026.5.27 allows remote authenticated users to obtain Bot Framework tokens via outbound requests. The Teams send/update/delete paths attach Bot Framework credentials to untrusted serviceUrl hosts without validating the destination trust boundary. Exploitation requires the integration to be enabled and lower-trust input to reach those paths; the documented consequence is credential disclosure, not code execution.
Summary
What happened
Token leakage in @openclaw/msteams before 2026.5.27 allows remote authenticated users to obtain Bot Framework tokens via outbound requests. The Teams send/update/delete paths attach Bot Framework credentials to untrusted serviceUrl hosts without validating the destination trust boundary. Exploitation requires the integration to be enabled and lower-trust input to reach those paths; the documented consequence is credential disclosure, not code execution.
The record
- CVE
- CVE-2026-62213
- Published
- Jul 17, 2026
- Updated
- Oct 8, 2026
- Vendor
- OpenClaw Foundation
- Product
- @openclaw/msteams
- Classifications
- CWE-522, CWE-441, CWE-200, T1528
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 17, 2026CVE publishedPublication date reported by the CVE source.
- Oct 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2026.5.27
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started