What problem does it solve?
Security testers assessing RAG-backed applications lack a structured methodology for finding vulnerabilities in the vector storage and retrieval layer, such as cross-tenant data leaks, unauthenticated vector databases, and persistent corpus poisoning that survives across sessions.
Core Features & Use Cases
- Persistent Corpus Poisoning Testing: Upload poisoned documents and verify the payload reaches a second, clean session via semantic retrieval on unrelated queries.
- Cross-Tenant Vector-Store IDOR Detection: Probe directly reachable vector databases (Chroma, Qdrant, Weaviate, Milvus, pgvector) and app APIs for missing tenant isolation, with a verifiable-artifact proof standard.
- Source-Text and Metadata Leakage Checks: Inspect similarity-search and sources endpoints for raw chunk text exposure, and distinguish metadata leaks from true embedding inversion.
- Use Case: While testing a multi-tenant SaaS chatbot with document upload, use this Skill to check whether an unauthenticated Qdrant port exposes the full corpus and whether another tenant's documents appear in your similarity results.
Quick Start
Ask the assistant to assess the target RAG application for vector-store isolation weaknesses, exposed vector-DB ports, and persistent corpus poisoning using the hunt-rag-vector methodology.