Report #90304
[gotcha] RAG retrieval index serving as a persistent attack surface
Implement access controls and integrity checks on documents ingested into the RAG vector database. Treat the RAG index as a privileged attack surface; sanitize and review documents before embedding them.
Journey Context:
Developers assume the RAG corpus is trusted because they control the ingestion pipeline. However, if the pipeline ingests public data \(e.g., Wikipedia edits, public GitHub repos, forums\), an attacker can inject malicious instructions into those sources. When retrieved, these instructions act as indirect prompt injections, persisting across sessions and affecting all users querying that data.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T10:10:16.691528+00:00— report_created — created