AI Stack Alert Medium CVE-2026-123271 For AppSec, AI Eng, SOC / IR AI-assisted
ChatCLI MCP OAuth flow leaks bearer token to other resources on same auth server (CVE-2026-123271)
ChatCLI versions before v1.215.2 do not validate the server-supplied Protected Resource Metadata in the MCP OAuth login flow. The metadata is used as the resource indicator without checking it matches the configured server URL. A malicious MCP server can declare a different resource on the same authorization server and obtain the user's bearer token for it.
Why it matters
A malicious or compromised MCP server can receive a user's OAuth bearer token and replay it against another resource on the same authorization server. Users who connect ChatCLI to untrusted MCP servers are exposed to token theft and unauthorized access to other services.
Do this
- Upgrade ChatCLI to v1.215.2 or later.
- Until upgraded, connect only to MCP servers that are trusted, and avoid adding unknown MCP servers to ChatCLI.
- Review OAuth tokens issued through ChatCLI MCP logins and rotate any that may have been issued to untrusted servers.
- Check authorization server logs for tokens issued for resources not expected for ChatCLI users.
- Where possible, configure the authorization server to restrict token audience to specific resource URIs.
Exploit Clock
Exploitation unlikely (for now)
- EPSS 0.15%
Signals
- NoCISA KEV
- 5.1CVSS
- 0.15%EPSS
- NoPublic PoC
- 26/100Priority
- 70%Confidence
Evidence
“A malicious MCP server can declare another resource on the same authorization server, obtain the user's bearer token for it, and replay that token against the other resource.”
“uses server-supplied Protected Resource Metadata as the resource indicator without checking it matches the configured server URL”
Sources
Affected / related
ChatCLI, MCP OAuth login flow, Protected Resource Metadata
Published 2026-11-05 19:17 UTC · updated 2026-11-08 02:28 UTC · AI-assisted summary, checked against quoted sources · How we score