Browse / AI Framework and Platform Flaws / Authentication and access control
Authentication and access control
256 records in AI Framework and Platform Flaws.
- milvus: RBAC grantee-id uses truncated MD5 (64-bit), enabling privilege-binding collisions and cross-role privilege forgery Milvus derives RBAC grantee identifiers from a truncated 64-bit MD5, so a local attacker can craft colliding names to inherit another role's privileges.
- PraisonAI `deploy --type api` emits a Flask server with authentication disabled by default A code generator emits a Flask API server with authentication off by default, leaving agent endpoints open to any client that can reach it.
- PraisonAI call server exposes unauthenticated agent listing, invocation, and deletion when CALL_SERVER_TOKEN is unset When the token variable is unset, the auth dependency returns success, leaving agent list, invoke and delete endpoints open to anyone who can reach them.
- Gradio contains a cookie injection vulnerability A proxy's shared HTTP client stores and replays a parent-domain cookie set by an attacker's Space into other users' requests.
- MLflow allows unauthorized access to multipart upload endpoints when the `--serve-artifacts` mode is enabled Multipart upload endpoints for artifacts skip per-resource permission checks, letting users overwrite other users' artifacts, which can later be loaded as poisoned models.
- LiteLLM allows an authenticated internal_user to create API keys with access to routes that their role does not permit API keys can be issued with routes outside the creator's role, and the gateway then honours them for admin endpoints.
- LiteLLM allows a user to modify their own user_role via the /user/update endpoint The user update endpoint checks account ownership but not which fields change, so a user can set their own role to proxy admin.
- MLflow authenticated users can enumerate any registered model versions due to lack of per-model permissions checks The model version search endpoint and GraphQL field skip per-model permission checks, so any authenticated user can list all versions and metadata.
- Flowise: Mass Assignment in PUT /api/v1/user Allows Authenticated Users to Override Password Hash and Bypass Password Change Verification The user update endpoint forwards the whole request body to the service, so a logged-in user can overwrite their stored password hash and skip the old-password check.
- MLflow: unauthenticated access to certain FastAPI routes Authentication is enforced only on gateway paths, so unauthenticated requests reach job and trace ingestion FastAPI routes under uvicorn.
- Open WebUI: shared-chat branch ignores access_type, allowing unauthorized file deletion The file access check grants access to any file referenced by any shared chat without checking the requesting user or the operation, so any user can delete others' files.
- Open WebUI Vulnerable to IDOR: Retrieval API Bypasses Knowledge Base Access Controls The collection access check skips knowledge base UUIDs, so any logged-in user who knows one can read or write that private knowledge base through retrieval endpoints.
- Open WebUI's API key endpoint restrictions bypassed via `x-api-key` header — full message processing on restricted endpoints Endpoint restrictions are enforced only for keys sent in the Authorization header, so the same key sent as x-api-key skips them.
- Open WebUI has an IDOR vulnerability in the pin_channel_message API endpoint Pin and unpin actions only check read permission on channel messages, so read-only members can change the pin state of any message.
- Open WebUI Vulnerable to Unauthenticated RAG Configuration Disclosure Open WebUI's RAG status route omits the authentication dependency that sibling routes use, so anyone can read the retrieval pipeline configuration.
- Open WebUI: Low-privilege authenticated users can enumerate and stop global background tasks, causing system-wide chat disruption Any verified user can list and cancel background tasks belonging to others, because the task endpoints never check task ownership.
- Open WebUI has Broken Access Control for Completions API Any API key holder can post completions into another user's chat by supplying its ID, because the server never checks who owns that chat.
- Open WebUI missing authorization check at the model update function - models from other users can be updated The model update endpoint does not verify ownership or write access, so any user can modify another user's private model.
- Open WebUI: LDAP and OAuth First-User Race Condition Allows Multiple Admin Accounts The first-user admin role is chosen before the user row is inserted, so concurrent logins on an empty instance can all receive admin.
- Open WebUI: Read-Only Users Can Toggle Note Pin Status via Incorrect Permission Check (Write via Read-Only Access) The note pin endpoint checks only read access, so a read-only collaborator can change pin state that should require write permission.
- Open WebUI: Cross-User File Access via Unchecked file_id in Folder Knowledge and Knowledge-Base Attach Endpoints Attach endpoints accept any file identifier without checking ownership, so an authenticated user can pull other users' files into their own retrieval context.
- Open WebUI: Missing permission check in files API allows authenticated users to list, access and delete every uploaded file File routes check only that a user is logged in and never filter by owner, so any account can list, read and delete other users' uploads.
- Open WebUI: Mass Assignment via FeedbackForm extra=allow Allows Feedback User ID Spoofing and Evaluation Data Manipulation Extra fields in feedback requests override the server-derived user ID, so records are attributed to other users.
- Open WebUI: Authenticated users can bypass model access control via exposed query parameter [AI-ASSISTED] An internal flag is bound from the URL query string, letting any logged-in user skip model access checks and call restricted models.
- Open WebUI has an IDOR vulnerability in the update_message_by_id API endpoint Group and DM channels only check membership when updating a message, so any member can edit messages written by other members.
- Open WebUI has an Indirect Object Reference (IDOR) in user notes The notes API does not check ownership, so any logged-in user can read other users' notes by ID.
- FlowiseAI: Dataset create+update mass-assignment allows cross-workspace dataset takeover Dataset create and update copy the entire request body onto the entity, letting a caller set workspaceId and id and move records across workspaces.
- FlowiseAI has Mass Assignment in Chatflow Update Endpoint that Allows Cross-Workspace AgentFlow Reassignment The chatflow update endpoint merges client-supplied fields such as workspaceId and deployed into the record, letting users move flows across workspaces.
- FlowiseAI has Mass Assignment in Variable Update Endpoint that Allows Cross-Workspace Resource Reassignment An authenticated user can submit server-controlled fields such as workspaceId in a variable update, moving variables into other workspaces.
- FlowiseAI: CustomTemplate create+update mass-assignment allows cross-workspace template takeover Object.assign copies a client-supplied workspaceId into a template record, letting a user take over templates in another workspace.
- FlowiseAI: Assistant create+update mass-assignment allows cross-workspace assistant takeover Client request bodies are copied directly onto the assistant record, so a caller can set the workspace identifier and access or overwrite another workspace's data.
- FlowiseAI: DatasetRow create+update mass-assignment allows cross-workspace row takeover Copying the full request body onto a database entity lets a client set its own workspace ID and move rows into another tenant's workspace.
- FlowiseAI: Vector Store No Permission Checks Vector store API routes lack permission middleware, so any logged-in user with a valid key can create, modify, upload to or delete stores they do not own.
- FlowiseAI has Mass Assignment in Assistant Update Endpoint that Allows Cross-Workspace Resource Reassignment The assistant update endpoint copies client-supplied server-owned fields such as workspaceId into the database, letting users move assistants across workspaces.
- FlowiseAI: Evaluation create+update mass-assignment allows cross-workspace evaluation takeover Object.assign copies a client-supplied workspaceId and id onto evaluations, letting an attacker move or access records belonging to other workspaces.
- FlowiseAI Exposes Basic Auth Credentials via API The basic auth check compares plaintext credentials with no rate limiting and returns distinct responses, letting attackers brute-force or enumerate logins.
- FlowiseAI: Evaluator create+update mass-assignment allows cross-workspace evaluator takeover Object.assign copies a client-supplied workspaceId into evaluator rows, letting a request move records into another workspace.
- FlowiseAI has Mass Assignment in Tool Update Endpoint that Allows Cross-Workspace Resource Reassignment The tool update endpoint merges client-supplied JSON into the database record, letting users reassign tools to other workspaces.
- n8n Has a Cross-user Authorization Bypass in Dynamic Credential OAuth Endpoints OAuth reconnect endpoints check read permission instead of update, so read-only users can replace stored credential tokens with their own.
- mem0 server lacks authentication and authorization controls for its memory deletion API endpoint The mem0 DELETE /memories route has no authentication or ownership check, so any caller can erase memories for arbitrary user identifiers.
- mem0 server lacks authentication and authorization controls for its memory management API endpoints The mem0 server exposes memory update and delete endpoints without checking the caller, so unauthenticated clients can alter stored memory records.
- Open WebUI has inconsistent authorization controls within memories API Memory endpoints do not consistently enforce ownership, letting any user query, view, delete and restore memories that belong to other users.
- Open WebUI's Improper Authorization in Standard Channels Allows Message Updates with Read Permission Message update in standard channels checks only read permission, so any user with read access can edit messages written by other users.
- Open WebUI's Insecure Message Access Breaks Authorization Channel message update and delete endpoints check channel access but not message ownership, letting users change other users' messages by calling the API directly.
- PraisonAI ships and generates a legacy API server with authentication disabled by default, allowing unauthenticated workflow execution The legacy server ships with authentication disabled, so anyone who can reach it can trigger the configured agent workflow without a token.
- Open WebUI has an LDAP Empty Password Authentication Bypass An LDAP login with an empty password succeeds on servers that accept unauthenticated simple bind, issuing a session for the target user.
- Open WebUI: Stale Admin Role in Socket.IO Session Pool Enables Post-Demotion Cross-User Note Access Socket.IO sessions keep the admin role captured at connect time, so a demoted user can still join and save restricted collaborative documents.
- Open WebUI has Improper Authorization Control Users pending approval can call the API directly because the role check exists only in the client interface, not on the server.
- Open WebUI's Channel Access Grants Bypass filter_allowed_access_grants Channel create and update endpoints store access grants without the permission filter other resources apply, so users can set public wildcard grants.
- Open WebUI's Base Model Routing Bypasses Access Control via Model Chaining Composed models can point base_model_id at a restricted model, and the chained base model's access is never checked at request time or creation.