Bypasses / Authorisation check
Authorisation check
147 cases that got past this protection.
- n8n: Privilege Escalation and Code Execution via Full Public API Key Scope Assignment to Token Exchange JWTs Tokens minted by the token exchange flow received every Public API scope regardless of the user's role, letting low-privileged callers perform administrator operations.
- n8n: Shared-Workflow Editor Can Exfiltrate Credentials via Inline Sub-Workflow JSON Credential checks inspect only top-level node credentials, so an editor can reference other credentials inside a sub-workflow's inline JSON and use them.
- n8n: External Secrets Permission Bypass via Expression Parser Mismatch Expression parsing misses some secret-reference forms, so a user can embed secrets they lack permission to read into credentials.
- n8n: Shared Credential Header Leak via HTTP Request Pagination Expression A user with use-only workflow access reads a shared HTTP Header Auth secret from pagination request state, then copies it into item data and sends it onward.
- n8n: AI Agents Project Viewer Privilege Escalation via run_node_tool A read-only project user could chat with an agent whose node tool ran with project credentials, skipping execution and credential permission checks.
- MCP Python SDK: Experimental task handlers allow any client to access and cancel other clients' tasks Experimental MCP task handlers never checked which session created a task, so any connected client could list, read and cancel other clients' tasks.
- MCP Python SDK: HTTP transports serve session requests without verifying the authenticated principal The session lookup checks only the session ID, so a different authenticated client can inject messages into someone else's session.
- MLflow: trace API endpoints lack proper authorization validators Trace API routes skip authorization validators, so any authenticated user can read or change traces in experiments they cannot access.
- LiteLLM: Admin Key Handler Has Improper Authorization A remote caller could reach a LiteLLM key management handler that fails to verify authorization, enabling administrative key operations.
- LiteLLM: M2M JWT Handler Has Improper Authorization A flaw in the machine-to-machine JWT handler causes improper authorization, letting remote attackers gain access they should not have.
- Langflow: IDOR Vulnerability in `/api/v1/responses` Endpoint Allows Authenticated Attackers to Access Another User's Flow Flows fetched by UUID are not checked against the requesting user, so any authenticated user can run another user's flow.
- PraisonAI Slack app_mention bypasses configured user/channel authorization The Slack mention handler lacks the user and channel allowlist checks present in the message handler, so unauthorised senders can trigger the agent.
- PraisonAI recipe.run_stream skips dangerous-tool policy enforcement The streaming recipe path skips the dangerous-tool policy check, so a recipe declaring a shell execution tool runs it without the required explicit opt-in.
- Open WebUI Prompt history IDOR: unbound history_id allows cross-prompt read and deletion The prompt history endpoints check the parent prompt but not that the supplied history entry belongs to it, so another user's history can be read or deleted.
- Open WebUI: Any authenticated user can read other users' private notes via Socket.IO A Socket.IO join handler skips its ownership check when a note's document ID uses an underscore instead of a colon, and the storage layer maps both forms to the same document.
- Open WebUI: Authenticated users can target arbitrary configured Ollama backends via unguarded url_idx path parameter A signed-in user adds a raw backend index to Ollama proxy routes, so requests reach backends that their model permissions never covered.
- Open WebUI BOLA: `search_knowledge_files` Allows Unauthorized Knowledge Base File Enumeration An authenticated user can make the model call the built-in knowledge search tool with an arbitrary knowledge base ID, and the tool returns file metadata without an access check.
- Open WebUI IDOR: Calendar event re-parenting allows writing events into another user's calendar The event update endpoint checks write access only on the source calendar, not the destination ID in the body, so events can be moved into others' calendars.
- Open WebUI: RAG ACL Bypass in Milvus Multitenancy Mode A collection name the ACL treats as legacy is interpolated unescaped into a Milvus filter, so crafted quotes make the filter return other users' knowledge-base chunks.
- Open WebUI: Forged model meta.knowledge allows cross-user file read and deletion Model metadata accepts file IDs without checking the owner's access, and the view and file endpoints trust them, letting the owner read or delete others' files.
- Open WebUI: Forged chat-file link allows cross-user file read and deletion Message file IDs are stored without ownership checks, and a shared chat then grants access to those files, letting an attacker read or delete other users' files.
- Open WebUI: Cross-user file disclosure via /api/chat/completions image_url field An authenticated user passes another user's file ID as an image URL, and the server reads that file without an ownership check and sends its contents to the model.
- n8n: Cross-Tenant Credential Takeover via Dynamic Credentials EE Endpoints Dynamic credential endpoints skip ownership checks, so any logged-in user can read or overwrite another tenant's credential tokens.
- n8n: Public API Execution Retry Authorization Bypass The public API retry endpoint checks workflow read permission instead of execute permission, so read-only sharing users can re-run executions.
- n8n: Wrong OAuth Scope On Evaluations Test Run Creation Endpoint The test-run endpoint checks only read permission, so users who can view a workflow can start an execution they are not allowed to run.
- n8n: Credential Exfiltration via Permission Bypass Some public API routes resolve credentials without full ownership checks, so an editor can reference and use credentials belonging to other users.
- ChromaDB's SimpleRBACAuthorizationProvider doesn't check which tenant, database, or collection a permission applies to The RBAC provider verifies that a permission is held without checking which tenant, database or collection it covers, enabling cross-tenant actions.
- MLflow: Any authenticated user can enumerate all gateway secrets, endpoints, and model definitions Any authenticated user can call three gateway list endpoints that lack authorization handlers, retrieving all gateway secrets, endpoints and model definitions.
- 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.
- MCP Server Kubernetes: Tool Access Control Bypass via Presentation-Layer Filtering Without Execution-Layer Enforcement The MCP server filters tools only in the listing step, so a client that knows a tool name can call it directly, ignoring the restriction.
- Flowise: Cross-Workspace Chatflow Disclosure via chatflows/apikey Endpoint Returns All Unprotected Chatflows The chatflow-by-API-key route returns every unassigned chatflow in the whole system, so a key from one workspace reads configurations from other workspaces.
- 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: Jupyter code execution works despite `ENABLE_CODE_EXECUTION=false` — feature gate bypassed The Open WebUI code execution endpoint forwards Python to Jupyter without checking the ENABLE_CODE_EXECUTION setting, so any verified user can run code.
- 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 chat completion API allows tool restrictions to be bypassed The chat completion endpoint runs any server tool named by ID without checking the caller's permission, using the server's stored credentials.
- 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 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: 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.
- 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 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.