Browse / RAG and Vector Store Weaknesses / Authentication and access control
Authentication and access control
10 records in RAG and Vector Store Weaknesses.
- Open WebUI: Inaccessible knowledge bases are exposed through the built-in knowledge tool on most vector backends
- Open WebUI: Model meta.knowledge read-only file access can be upgraded to file write/delete A model's knowledge-file metadata lets a read-only grant satisfy later write and delete checks, because an earlier fix validated only read access.
- Open WebUI: Cross-user file disclosure via /api/chat/completions image_url field
- ChromaDB allows any authenticated users to arbitrarily read, write, update, or delete data in any tenant's collection The vector database omits authorisation checks, so any authenticated user can read and modify collections belonging to other tenants.
- Open WebUI: Cross-User File Access via Unchecked file_id in Folder Knowledge and Knowledge-Base Attach Endpoints
- FlowiseAI: Vector Store No Permission Checks
- Open WebUI has Knowledge Base Destruction and RAG Poisoning via Unauthorized Collection Overwrite A web-retrieval endpoint accepts any collection name and overwrites it without ownership checks, so other users' vector collections can be deleted or poisoned.
- Open WebUI has Unauthorized File and Knowledge Base Content Access via RAG Vector Search
- Open WebUI's responses passthrough endpoint lacks access control authorization
- Lobe Chat has IDOR in Knowledge Base File Removal that Allows Cross User File Deletion