Browse / AI Framework and Platform Flaws / Authentication and access control
Authentication and access control
261 records in AI Framework and Platform Flaws.
- Kubeflow Pipelines: Cross-tenant execution-cache poisoning / output substitution via a namespace-blind cache key in the cache webhook (multi-user) The pipeline step cache key omits the tenant namespace, letting one tenant read or pre-populate cached outputs belonging to another tenant.
- Kubeflow Pipelines: RBAC bypass on shared pipelines allows any authenticated user to delete or modify global pipelines
- Kubeflow Pipelines API server lacks authorization for shared pipeline uploads
- Kubeflow Pipelines: Run-log endpoint permits unauthorized access to pod logs
- LiteLLM: Privilege Escalation to Proxy Admin via Cross-Domain Reuse of the Salt Key Reusing one encryption key for both secret storage and session tokens lets an internal user forge an admin token via a crafted key metadata field.
- LangGraph: Namespace labels containing `.` reach other namespaces in Postgres and SQLite stores Namespace label validation runs only on writes, so dotted labels in reads, deletes and batches reach other namespaces' stored data.
- vLLM: Forged multimodal UUID + P0/P1 processor-cache eviction drift: unauthenticated remote crash of the whole vLLM engine
- PraisonAI: Call API localhost-only authentication bypass via spoofed Host header The localhost-only exemption from auth trusts the request Host header, so a spoofed Host value lets remote callers invoke agents unauthenticated.
- Pydantic AI Web chat UI (`Agent.to_web()`, `clai web`): a website visited by the developer can trigger agent runs and server-side tool execution on the local chat endpoint
- Pydantic AI Web chat UI (`Agent.to_web()`, `clai web`): the local chat endpoint does not validate the `Host` header
- Langflow : Cross-user flow access and vertex execution via deprecated /api/v1/build/{flow_id}/vertices endpoints
- PraisonAI: AgentMail webhook mode accepts forged unsigned message.received events and invokes agents A public webhook endpoint accepts unsigned message events and dispatches them to agents, so anyone can forge inbound messages that trigger agent replies.
- Docling: `enable_local_fetch` is not enforced in HTML browser-rendering mode
- Langflow: Unauthenticated Flow Execution via Webhook Authentication Bypass When a config flag is off, webhook calls skip API key checks, so anyone who knows a flow UUID can run that flow as its owner.
- vm2: NodeVM custom resolution bypasses external path boundaries
- vm2: Sandboxed code can read and write host-realm memory via Node's shared Buffer pool
- 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: Admin demoted through SSO role sync keeps read and write access to all users' notes
- Open WebUI: Sign-in as another user via wildcard characters in the OAuth subject claim on SQLite
- Open WebUI: Users denied by the OAuth role policy can still sign in via token exchange
- n8n: Anonymous Approval-Gate Bypass via Reused resumeToken over the Chat WebSocket A reused resume token from a public form lets an anonymous party resume a paused workflow through the chat route, bypassing the approval gate that should hold it.
- n8n: GitHub Trigger 422 Reuse Path Skips Webhook Secret Storage, Causing Signature Verification to Fail-Open After a 422 reuse path the stored webhook signing secret is discarded, so signature verification accepts unsigned deliveries.
- n8n: Cross-User Active Workflow ID and Lifecycle Event Disclosure via Missing userId Filter n8n's active-workflows endpoint and push events skip the per-user sharing filter, so members can see workflow IDs and activity they should not access.
- 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: Disabled OIDC SSO Endpoints Remain Active and Issue Valid Sessions
- n8n: Log Streaming Event Destinations Decrypt Generic-Auth Credentials Without Ownership Check
- PraisonAI: [Auth Bypass] PraisonAI async Jobs API (`/api/v1/runs`) has no authentication — unauthenticated job execution, result theft, cancel and delete The jobs API router has no authentication, so any reachable caller can submit, read, cancel and delete agent jobs.
- PraisonAI serve agents --api-key is ignored, allowing unauthenticated remote agent execution The configured API key is never checked on the agent invocation endpoints, so unauthenticated network callers can run agents.
- PraisonAI: Authentication fail-open in Recipe server allows unauthenticated access when API key or JWT auth is configured without a secret
- PraisonAI: `--api-key` flag on `praisonai serve` is not properly enforced
- praisonaiagents: AgentServer declares auth_token but never enforces it on any route AgentServer stores an auth_token setting but no route checks it, so unauthenticated clients can reach every endpoint.
- New API: Admin can reset passkeys for same-level or higher-privileged users
- vm2: NodeVM `builtin: ['*']` exposes `os` and `dns` — process-wide observability reads AND writes that hijack the host (sibling class of GHSA-9g8x-92q2-p28f)
- 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: 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
- 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
- Open WebUI: Any member with write access to a standard channel can edit or delete other members' messages
- Open WebUI: Account takeover via OAuth token exchange accepting tokens issued to any client
- Flowise: IDOR vulnerability exists at the GET /api/v1/organization/customer-default-source endpoint An authenticated user can request another customer's payment and profile data by changing the customerId parameter, because object-level ownership is not checked.
- 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: 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