WeaknessASC-2026-0034Other weakness
Confused deputy and token passthrough in MCP servers
MediumFixed
MCP servers that forward the client's token to downstream APIs, or act with their own broad identity for any caller, let one user or injected prompt act with someone else's access.
How to detect it
- Servers that accept tokens not issued for them
- Servers using one service account for all users
How to resolve it
- Validate that tokens were issued for the MCP server (audience) and never pass them through
- Act with per-user, least-privilege credentials
- Follow the MCP authorization specification
How to investigate
- Review downstream API logs for actions attributed to the server's identity
- Map which users triggered them