OpenClaw MS Teams inbound attachment downloader leaks bearer tokens to allowlisted suffix domains

Summary

NOTE: This only affects deployments that enable the optional MS Teams extension (Teams channel). If you do not use MS Teams, you are not impacted.

When OpenClaw downloads inbound MS Teams attachments / inline images, it may retry a URL with an Authorization: Bearer <token> header after receiving 401 or 403.

Because the default download allowlist uses suffix matching (and includes some multi-tenant suffix domains), a message that references an untrusted but allowlisted host could cause that bearer token to be sent to the wrong place.

Affected Packages / Versions

• Package: openclaw (npm)
• Vulnerable: <= 2026.1.30
• Patched: >= 2026.2.1

Fix

• Fix commit: 41cc5bcd4f1d434ad1bbdfa55b56f25025ecbf6b
• Upgrade to openclaw >= 2026.2.1

Workarounds

• If you do not need MS Teams, disable the MS Teams extension.
• If you must stay on an older version, ensure the auth host allowlist is strict (only Microsoft-owned endpoints that require auth) and avoid wildcard or broad suffix entries.

Credits

Thanks @yueyueL for reporting.