Products / flowise
flowise
114 records.
- Flowise NodeVM sandbox escape via puppeteer allowlist - authenticated RCE and arbitrary file read via Chromium An authenticated user passes executable path and args to puppeteer.launch from the sandboxed custom function, spawning host commands outside the sandbox.
- Flowise Prompt Injection to RCE and SSRF via CSV/Airtable Agent Python Validator Bypass Prompt-injected LLM output in CSV and Airtable agents supplies Python that evades a regex blocklist and uses pandas URL readers to send data to attacker hosts.
- Flowise: RCE via NodeVM Sandbox Escape in executeJavaScriptCode() nodeVMOptions Override Caller-supplied VM options spread over secure defaults re-enable blocked built-in modules, letting an authenticated user escape the sandbox and run system commands.
- Flowise: RCE via CSVAgent csvFile data URI base64 segment is interpolated into Python source without validation Unvalidated CSV file data is spliced into Python code run by an agent sandbox, so a crafted value escapes into Node and runs commands.
- Flowise: Pyodide validator Unicode homoglyph bypass leads to RCE A regex blacklist on generated Python misses Unicode homoglyph identifiers that Python normalises to dunder names, so forbidden access to builtins runs in the sandbox.
- Flowise: CSV Agent Prompt Injection Remote Code Execution Vulnerability A prompt sent to a CSV agent chatflow makes the model emit Python that evades the blocklist and runs in the server's Pyodide-based sandbox.
- Flowise: Authenticated arbitrary file write in the `S3 Directory` document loader via unsanitized S3 object keys Attacker-chosen S3 object keys are joined into local paths without stripping traversal sequences, so files are written outside the temporary directory.
- Flowise RCE via TypeORM DataSource Authenticated users can pass arbitrary options into a TypeORM DataSource through node settings, which can be abused to execute code on the server.
- Flowise: CSV Agent Remote Code Execution via Pyodide Code Injection — Root Shell Verified Unsanitised CSV agent input is inserted into Python code run in Pyodide, and the JS bridge lets that code reach the host Node process to run OS commands.
- Flowise Sandbox Escape to RCE A JavaScript escape from the Flowise custom function sandbox lets user code reach the host process and run arbitrary commands.
- Flowise RCE via SQLite Record Manager Node The SQLite record manager node lets additionalConfig override its database path, enabling attacker-chosen file writes that lead to code execution.
- Flowise: Remote Code Execution Vulnerability in CSVAgent The CSV agent runs user-supplied Python through a denylist that misses pandas read_pickle, letting a pickle payload execute code.
- Flowise: CVE-2025-8943 Patch Bypass: npm_config_yes bypasses MCP environment variable blocklist (Unauthenticated RCE) Setting npm_config_yes through the MCP server environment makes npx auto-install and run an arbitrary package, because only four environment names are blocked.
- 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: 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: SSRF Protection Bypass via IPv4-Mapped IPv6 Addresses Private IPv4 deny rules are skipped when an IPv4-mapped IPv6 address is used, so hostnames resolving to such addresses reach internal targets.
- 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: Information Disclosure in GET /api/v1/upsert-history returns the entire server-wide upsert history The upsert history endpoint returns every workspace's ingestion records without scoping, exposing vector store endpoints and collection names.
- 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: Unauthenticated OAuth2 token refresh endpoint returns access tokens — enables token theft for any connected service An unauthenticated route returns freshly refreshed OAuth access tokens, so anyone holding a credential ID can take them and use the victim's connected services.
- Flowise: Unauthenticated OAuth2 Refresh Enables Non-Blind SSRF and Secret Exfiltration The OAuth2 refresh route is whitelisted from auth and sends server-side requests to a credential-supplied token URL without SSRF checks, returning the remote response to the caller.
- Flowise: Incomplete Credential Redaction Exposes Secrets via API The credential endpoint redacts only password-typed fields, so secrets stored in string fields such as URLs and keys are returned in plaintext.
- Flowise: Cross-Workspace OAuth2 Credential Metadata Leak Flowise OAuth2 endpoints look up credentials by ID alone, so authenticated users reach other workspaces' credentials and unauthenticated callers can overwrite tokens.
- 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.
- 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.
- 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.
- Flowise: Hardcoded CORS wildcard on TTS endpoint enables cross-origin credential abuse from any webpage A hardcoded wildcard CORS header on the TTS endpoint lets any website make cross-origin requests that use stored credentials.
- Flowise has an MCP Security Bypass that Enables RCE A custom MCP server config running docker build with a remote URL slips past a flag blocklist that omits build, so a remote Dockerfile executes commands.
- 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 Vulnerable to Credential Data Leak Credential lookups with a name filter return the encrypted data field, which the unfiltered path strips, exposing stored API secrets.
- 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: Authenticated Host RCE via POST /api/v1/node-custom-function and NodeVM Sandbox Escape A signed-in user posts JavaScript to a custom function endpoint with no route permission check, then escapes the NodeVM sandbox to reach host child_process.
- 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.
- Flowise: Bcrypt Password Hash Exposure The Flowise login handler returns bcrypt password hashes in its response, so a remote caller can obtain other users' hashes.
- Flowise: CSV Agent Prompt Injection Remote Code Execution Vulnerability The CSV agent runs Python scripts generated by the LLM without sandboxing, so a crafted prompt makes the server execute attacker-chosen code without authentication.
- Flowise: Airtable_Agent Code Injection Remote Code Execution Vulnerability Flowise executes Python generated by an LLM in the Airtable agent without sandboxing, so a crafted prompt can run code on the server.
- Flowise: Mass Assignment in DocumentStore Create Endpoint Leads to Cross-Workspace Object Takeover (IDOR) The create endpoint accepts a client-supplied primary key and saves the whole body, so it overwrites existing document stores owned by other workspaces.