MS Teams outbound requests could leak Bot Framework tokens
GHSA-v54h-q2vx-vgg4 · published 2026-06-30
- Severity
- Medium
- CVSS score
- 6.5
- Chance of exploitation (EPSS)
- No CVE
- Fixed in
- 2026.5.27
When the affected feature is enabled and reachable, this could expose data or credentials that should have remained within the trusted boundary. Practical impact depends on the operator's configuration and whether lower-trust input can reach that path.
Upgrade @openclaw/msteams to 2026.5.27 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.
The first stable patched version is 2026.5.27.
Upgrade to a patched OpenClaw release when one is listed. Before upgrading, restrict the affected feature to trusted operators or disable it when it is not needed. As general hardening, keep channel and tool allowlists narrow, avoid sharing one Gateway between mutually untrusted users, and disable the affected feature when it is not needed.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| @openclaw/msteams | npm | < 2026.5.27 | 2026.5.27 |
- CriticalMLflow: Unauthenticated full-read SSRF in webhook delivery: _validate_webhook_url bypassed via unvalidated HTTP redirects (and DNS rebindingmlflowExploited
- Critical@zereight/mcp-gitlab Vulnerable to Server-Side Request Forgery@zereight/mcp-gitlab
- CriticalSSRF + LLM API key exfiltration via user-controlled basepath / baseUrl in 8 chat-model nodesflowise, flowise-components
- CriticalLocalAI POST /models/apply permits unauthenticated server-side request forgery through gallery URLsgithub.com/mudler/LocalAI
- CriticalFastMCP OpenAPI Provider has an SSRF & Path Traversal Vulnerabilityfastmcp
- CriticalBentoML SSRF Vulnerability in File Upload Processingbentoml
- MediumOpenClaw: Channel read actions could skip target allowlists@openclaw/feishu, @openclaw/googlechat, @openclaw/matrix, @openclaw/msteams
- Medium[AgentGG] MS Teams allowFrom could bind to mutable display names@openclaw/msteams
- MediumBot Framework serviceUrl validation could leak bot tokens@openclaw/msteams
The impact, patch and workaround text comes from the advisory, shortened (published by OpenClaw). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.