MCP Caching Flaw Can Expose One User's Private Data to Another Without Fix
The MCP specification (version 2026-07-28) introduced caching hints that allow servers to mark responses as public or private with a defined time-to-live. However, a shared client cache without proper partitioning can return one user's private cached result to a different user if cache keys do not account for authorization identity. A developer demonstrated this vulnerability by showing that Bob could receive Alice's private tool list from a shared cache when no cachePartition was set. The fix involves assigning each authorization context a stable, unique cache partition derived from a user or tenant identity, ensuring private entries remain isolated. The official TypeScript SDK v2 caching guide also warns about this misconfiguration, which can silently serve private response bodies across user sessions.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in