By Vero SecurityBuilt and funded by Vero Security, the AI Security Engineering platform.Read the charter

Agent memory poisoning

Persistent memory lets one successful injection keep influencing future sessions. Know how memory is written, give users and admins a way to review and clear it, and watch for memory writes triggered by untrusted content.

Read in this order

  1. OfficialAgentic AI: Threats and Mitigations (OWASP GenAI Security Project)Start here: where memory poisoning sits among agent threats and mitigations.
  2. ArticleChatGPT: Hacking Memories with Prompt Injection (Embrace The Red)A concrete exploit that planted false memories through prompt injection.
  3. PaperAgentPoison: Red-teaming LLM Agents via Poisoning Memory or Knowledge BasesResearch showing poisoned memory entries can steer agent behavior.

Save your progress

We email you a sign-in link. No password.

By signing in you agree to the terms. The privacy policy explains how we use your details.

Join the AI security engineering community

Free. Roadmap updates, chapters near you, and first word when credentials open.

We’ll email you community updates. Unsubscribe anytime. By sending this you agree to the terms. The privacy policy explains how we use your details.