Openclaw cli: OpenClaw MS Teams inbound attachment downloader leaks bearer tokens to allowlisted suffix domains
Affects openclaw-cliSource GCVE Database
Not known to be exploited · CVSS 7.4 High : upgrade to 2026.2.1 soon.
Data as of 16 Nov 2026, 20:25 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2026.2.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 13 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Upgrade openclaw-cli to 2026.2.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewopenclaw-clipkg:brew/openclaw-cliOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in openclaw version 2026.2.1 and later; upgrading to this version fully mitigates the vulnerability. If upgrading is not possible, disable the MS Teams extension to avoid exposure. Alternatively, restrict the authorization host allowlist to only include Microsoft-owned endpoints that require authentication, avoiding wildcard or broad suffix entries to prevent token leakage.
Description
OpenClaw CLI versions up to 2026.1.30 have a vulnerability in the MS Teams extension where bearer tokens used for authorization can be leaked to allowlisted suffix domains during attachment downloads. This occurs because the default allowlist uses suffix matching, potentially sending tokens to untrusted but allowlisted hosts. The issue is fixed in version 2026.2.1. Users not using MS Teams are not affected. Mitigation includes upgrading to 2026.2.1 or disabling the MS Teams extension if not needed.
References
- github.com/openclaw/openclaw/security/advisories/GHSA-7vwx-582j-j332 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-28481 (opens in a new tab)
- github.com/openclaw/openclaw/commit/41cc5bcd4f1d434ad1bbdfa55b56f25025ecbf6b (opens in a new tab)
- github.com/openclaw/openclaw (opens in a new tab)
- github.com/openclaw/openclaw/releases/tag/v2026.2.1 (opens in a new tab)
- vulncheck.com/advisories/openclaw-bearer-token-leakage-via-ms-teams-attachment-downloader-suffix-matching (opens in a new tab)