Bypasses / Authorisation check
Authorisation check
147 cases that got past this protection.
- Kubeflow Pipelines: RBAC bypass on shared pipelines allows any authenticated user to delete or modify global pipelines Multi-user mode skips authorisation for shared pipelines with an empty namespace on write and delete, letting any user modify or remove them.
- Kubeflow Pipelines API server lacks authorization for shared pipeline uploads Upload endpoints skip the access check when the namespace is empty, letting callers create or replace shared pipeline versions.
- Mem0: Cross-tenant conversation leak via unescaped delimiter collision in session-scope key (_build_session_scope) Conversation scope keys join caller-supplied identifiers with unescaped delimiters, so a crafted run_id can match another tenant's stored messages.
- Model Context Protocol Python SDK: Server bearer-token authentication accepts tokens issued for a different resource server The bearer token verifier does not check the audience, so tokens issued for other services are accepted by the MCP server.
- FastMCP: Post-transform component authorization is skipped on direct calls A server transform changes component metadata after authorisation, and direct lookups return the transformed component without rechecking policy, so denied tools and resources can be reached.
- Langflow : Cross-user flow access and vertex execution via deprecated /api/v1/build/{flow_id}/vertices endpoints Deprecated chat routes accept a flow ID without checking ownership, so any logged-in user can read and execute another user's flow vertices.
- Langflow: IP Spoofing Bypass via `X-Forwarded-For` Allowing Remote Configuration Write A spoofed X-Forwarded-For header makes the MCP install endpoint treat a remote request as local, allowing an MCP client config file to be overwritten.
- Langflow has Authenticated Cross-Project File Disclosure via Unscoped MCP Resource Handlers An authenticated user sends a crafted resource URI to their own project's MCP endpoint and reads another user's flow file, because the read is not authorised.
- MCP Atlassian: ENABLED_TOOLS / Toolset authorization bypass Tool filters are applied only when listing tools, so a direct tools/call request can invoke any registered tool by name, bypassing the configured restriction.
- Open WebUI: Non-admin users can delete admin-owned external knowledge connections via knowledge base deletion Deleting a knowledge base also deletes its shared admin-owned vector connection without checking the caller's role or other dependent bases.
- Open WebUI: Any authenticated user can inject chats into another user's folder via chat completions The chat-completions endpoint saves new chats into a folder named in the request without checking the caller's write permission on that folder.
- Open WebUI: Users denied by the OAuth domain allowlist or role policy can still sign in via token exchange The token exchange endpoint skips the email domain allowlist, so users removed from allowed domains still receive working sessions.
- Open WebUI: Channel members can overwrite another member's message via the chat completions endpoint A channel member can rewrite another member's message through the chat completions path, which skips the authorship check that the dedicated edit route applies.
- Open WebUI: Inaccessible knowledge bases are exposed through the built-in knowledge tool on most vector backends Several vector backends ignore the access filter on search, so the knowledge tool returns matches from knowledge bases the caller cannot read.
- Open WebUI: Admin demoted through SSO role sync keeps read and write access to all users' notes Demoting a user through SSO role sync does not close their open Socket.IO connection, so cached admin rights keep working on all users' notes.
- Open WebUI: Users denied by the OAuth role policy can still sign in via token exchange Token exchange issues sessions without re-running role management, so users whose provider role was revoked keep their previous access level.
- n8n: Cross-Tenant Project-Member PII Disclosure via Missing Per-Project Scope Check on Role Assignment Endpoints Role assignment endpoints check role permission but not project visibility, so a user can read members of any project by naming it.
- n8n: Per-Resource OAuth Consent Bypass via Unbound Refresh Token Resource Substitution Refresh requests were checked only for a registered resource, not against the resource in the original grant, so a token could be refreshed for a different protected workflow.
- n8n: Log Streaming Event Destinations Decrypt Generic-Auth Credentials Without Ownership Check Log streaming destinations decrypt any referenced generic credential without checking the caller's access, so a user can send another project's secret to an endpoint they control.
- n8n: Agent Workflow Tool Bypasses Sub-Workflow Caller Policy Agent tool invocations skip the sub-workflow caller restriction, letting a user who builds an agent run workflows the owner had locked down and read their output.
- New API: User List API Leaks Root User Access Token Leading to Privilege Escalation The admin user list API serialises each user's access token, so an admin can read the root account's bearer token and act as root.
- New API: Admin can reset passkeys for same-level or higher-privileged users A lower-privileged admin can reset passkeys of same-level or higher accounts because the reset endpoint skips the role comparison used by sibling endpoints.
- Feast vulnerable to arbitrary code execution via unsafe deserialization of dill-serialized UDFs Stored registry functions serialised with dill are deserialised by the server, so a malicious function placed in the registry runs code on the feature server.
- Open WebUI: A folder write-collaborator can permanently delete the owner's chats by deleting a shared subfolder Write access on a shared subfolder lets a collaborator delete the owner's chats, because the delete handler checks write access rather than ownership.
- Open WebUI: Tool source code disclosed to read-only users via the tool list and get endpoints Read endpoints for shared tools return the full Python source to non-writer users, exposing any credentials or internal URLs embedded in the code.
- Open WebUI: Any authenticated user can cancel another user's chat generation via the chat delete endpoint The chat delete endpoint cancels another user's in-flight generation tasks before checking whether the caller may delete that chat.
- Open WebUI: Unapproved accounts can open terminal sessions via a WebSocket auth path missing the role check The terminal WebSocket authenticates its own token and skips the verified-user role check, so pending accounts can open shell sessions.
- Open WebUI: Cross-user file content disclosure via request-scoped direct model knowledge metadata Knowledge attached to an inline model skips the access check, so an authenticated user who knows another user's file ID can retrieve its indexed content.
- Open WebUI: Users denied the image-generation permission can still generate images via chat completions Chat completion requests can include an image feature flag that the server honours without rechecking the user's revoked permission, so generation still runs.
- Open WebUI: Deletion of directories and file embeddings in other knowledge bases via sync cleanup A user with write access to one knowledge base can delete directories and embeddings in other knowledge bases because object ids are never checked for ownership.
- Open WebUI: Any member with write access to a standard channel can edit or delete other members' messages On standard channels, the message update and delete handlers never checked authorship, so any member with write access could change or delete others' messages.
- Flowise: Unauthenticated Property Injection into Flow Execution Context via Ungated `overrideConfig` Spread in Prediction API The unauthenticated prediction endpoint spreads caller-supplied overrideConfig into flow context without the override gate, letting attackers inject session and chat-related properties.
- Flowise: Unauthenticated Credential Abuse via Text-to-Speech Endpoint Allows Unauthorized Use of Private Chatflow TTS Credentials An unauthenticated caller can use a private chatflow's text-to-speech credentials by supplying its ID, because the route skips the public-access check.
- Flowise: RBAC Bypass Leading to Unauthorized Workspace Variables Disclosure A user denied variables view permission can run custom JavaScript that receives all workspace variables, including server environment values, because $vars is injected unconditionally.
- Flowise: Cross-workspace credential IDOR in openai-assistants-vector-store A client-supplied credential ID is used without checking that it belongs to the caller's workspace, letting one tenant use another tenant's OpenAI key.
- Flowise: Missing Authorization on Execution Update Endpoint A PUT route on execution records skips the permission middleware that sibling routes use, letting any authenticated user change any execution.
- Flowise: Broken Access Control in Stripe Subscription Endpoints Allows Cross-Tenant Billing Manipulation Billing routes accept a client-supplied Stripe subscription ID without checking it belongs to the caller's organisation, enabling changes to other tenants.
- Flowise: `DELETE /api/v1/chatflows/:id` does not validate resource type, allowing `agentflows:delete` and `chatflows:delete` to delete each other’s flow type The delete route accepts either permission but never checks flow type, so a key scoped to one flow kind can delete the other kind.
- Flowise: Missing authorization on `/api/v1/files` allows low-privileged API keys to list and delete files across workspaces within the same organization The files API checks only a feature flag, not per-permission authorisation, so any API key in an organisation can list and delete other workspaces' files.
- Open WebUI: Cross-user model-list exposure via static cache key in get_all_models (aiocache key= vs key_builder= misuse) A misused cache key stores per-user permission-filtered model lists under one shared key, so a different user can receive them within the TTL.
- Open WebUI: Private channel messages can be disclosed through cross-channel thread parent_id binding A low-privilege user requests a thread in an accessible channel and supplies a message id from a private channel as the root, so the parent message is returned without a channel membership check.
- Open WebUI: Cross-user code-interpreter and tool execution via unvalidated Socket.IO event-caller session_id A user supplies another user's socket session id, so code and tool calls run in the victim's session and can reach admin-only server-side function execution.
- Open WebUI: Upload `metadata.knowledge_id` bypasses the knowledge-base write-access check (read-only users can add files to KB) An upload carrying a knowledge base ID is linked to that knowledge base before the write-permission check runs, letting read-only users add files.
- Open WebUI: Arena task endpoints can bypass underlying model access controls Arena task routes call the generator directly, so the access check on a restricted submodel is skipped once the wrapper is authorised.
- Open WebUI: Scheduled automations continue after pending-user deactivation and stored model ACL revocation Scheduled automations keep running for deactivated pending accounts because the scheduler skips owner status checks and model access logic mishandles that role.
- Open WebUI: POST /api/v1/images/edit bypasses the global image-edit switch and the per-user image-generation permission An authenticated non-admin can call the image edit route, which skips the global edit switch and per-user permission, triggering billable provider requests.
- Open WebUI: Cross-channel message overwrite via chat completion API (single-model and multimodel message_ids) A channel-prefixed chat ID combined with a chosen message ID lets a user overwrite messages in channels they do not belong to.
- n8n: Improper Authorization Allows Authenticated Users to Assign Workflows to Folders in Other Projects A crafted creation request links a new workflow to a folder in another project because the server does not verify folder ownership.
- n8n: SSO Instance-Role Provisioning Allows Privilege Escalation to Instance Owner An SSO user whose identity provider sends an owner role claim is provisioned as instance owner, because the provisioning path skips the owner-role check.
- n8n: Credential Authorization Bypass via Expression in HTTP Request Node `genericAuthType` A workflow editor supplies the HTTP node credential type through an expression, so the permission check misses and another user's credential loads.