What problem does it solve? Security testers assessing RAG-backed applications often miss vulnerabilities in the vector storage and retrieval layer, such as cross-tenant data exposure, unauthenticated vector-DB APIs, and persistent corpus poisoning that survives across sessions. ## Core Features & Use Cases - Persistent Corpus Poisoning Testing: Upload a document with a hidden instruction and verify from a second clean session whether the payload is retrieved and executed on unrelated queries. - Cross-Tenant Vector-Store IDOR Checks: Probe directly reachable Chroma, Qdrant, Weaviate, Milvus, or pgvector endpoints and test app-level namespace or document-ID parameters for tenant isolation failures. - Source-Text and Metadata Leakage Detection: Inspect similarity-search and sources endpoints for raw chunk text or document IDs belonging to other tenants, and distinguish this from true embedding inversion. - Use Case: While testing a multi-tenant SaaS chatbot with document upload, you discover its Qdrant port is exposed, list all collections without credentials, and report an unauthenticated full corpus read as a Critical finding. ## Quick Start Use the hunt-rag-vector skill to test this RAG-based chat application for vector-store isolation flaws and persistent corpus poisoning.