Skip to the content
AI and Cybersecurity Learning and Practice Center Test automation Open the Learning Center

WeaknessASC-2026-0006Major weakness

Memory and context poisoning

HighWorkarounds only

Attackers write false facts or instructions into long-term memory or RAG stores that later sessions trust.

How to detect it

  • Persistent memory or a vector store accepts writes with no validation
  • Retrieved documents contain instruction phrases or hidden text

Workarounds

  • Validate and attribute every memory write (who, when, from which source)
  • Expire memory entries and review high-impact ones
  • Isolate stores per tenant and per trust level
  • Retrieve with provenance so untrusted chunks are labeled as data

No general fix exists for poisoned retrieval; controls limit how far a poisoned entry can spread.

How to investigate

  1. Find memory or RAG entries written from untrusted sources around the incident
  2. Run the content inspector on suspicious entries
  3. List sessions that retrieved the entry, purge it and re-index

Sources

Open it in the Learning Center's vulnerability database