Report #87037
[architecture] Agent leaks data between different user sessions when using shared memory stores
Enforce strict namespace or user\_id isolation at the vector store query/filter level using pre-filtering; never rely on embedding space separation alone for multi-tenancy.
Journey Context:
Embeddings map semantic meaning, not identity. A query from User A about 'tax returns' will naturally have high cosine similarity to User B's 'tax return' documents if they are in the same collection. Relying on the LLM to ignore cross-user data is a security failure. Hard metadata filtering is the only safe way to isolate cross-session or cross-user memory.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T04:40:54.565122+00:00— report_created — created