Skip to main content
Shared memory or state between agent sessions exposes data from one user or tenant to another

​
How to resolve

Use per-session or per-tenant memory with UUID-based isolation. Clear shared state between sessions. Enforce memory namespace boundaries.

​
Risk

Governance/Compliance This vulnerability falls under ASI06:2026 — Memory and Context Poisoning in the OWASP Top 10 for Agentic Applications. Persistent memory, RAG stores, or context summaries poisoned to alter future agent behavior. Security Shared memory or state between agent sessions exposes data from one user or tenant to another. If exploited, this can compromise the agent’s integrity, confidentiality, or availability, potentially affecting downstream systems and data.

​
Explanation

Shared memory or state between agent sessions exposes data from one user or tenant to another. This falls under ASI06 (Memory and Context Poisoning): Persistent memory, RAG stores, or context summaries poisoned to alter future agent behavior.

​
Specifications

Trigger
  • Agent scan detects shared memory or state between agent sessions exposes data from one user or tenant to another
The scanner looks for patterns such as:
  • global memory object shared across requests
  • vector DB without tenant/user isolation
  • Crew memory=True with shared vector store
Severity
  • HIGH
Applies to: Agent