UTC
Critical

SSRF + LLM API key exfiltration via user-controlled basepath / baseUrl in 8 chat-model nodes

CVE-2026-91935 · GHSA-hx55-h48h-7rw9 · published 2026-08-31 · updated 2026-09-20

Severity
Critical
CVSS score
9.4
Chance of exploitation (EPSS)
Not scored
Fixed in
3.1.4
  • Exploitation Public proof of concept
  • Automatable No
  • Technical impact Total
  • CISA SSVC
What it is

1. SSRF with full response read. Any workspace member with chatflow-edit permission can cause the Flowise server to issue HTTP POST requests to any reachable host — cloud metadata (169.254.169.254, metadata.google.internal), internal services (postgres:5432, redis:6379, internal admin dashboards), link-local, IPv6 loopback. Response is surfaced as the LLM chat output, so this is a read-anywhere primitive, not blind. 2. Cloud IAM credential theft on EC2/ECS/EKS/GKE. returns temporary AWS credentials. Flowise has no IMDS protection for these chat-model nodes. 3. LLM provider API key exfiltration. …

What to do

Upgrade flowise to 3.1.4 or later, and flowise-components to 3.1.4 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.

1. Reject private/loopback/link-local URLs in every chat-model node init() before constructing the LangChain client. The simplest fix is a shared helper that calls checkDenyList(basePath) from httpSecurity.ts at node-init time: 2. Configure LangChain's httpAgent to go through the Flowise SSRF proxy. The ChatOpenAI constructor accepts configuration.fetch — route it through a secureFetch-wrapped function that re-checks every URL, including redirects: 3. Apply the same fix to ChatOllama, ChatLocalAI, ChatLitellm, ChatNvdiaNIM, ChatNemoGuardrails, ChatCloudflareWorkersAI, ChatGoogleGenerativeAI. Each has its own init() that constructs a LangChain client; each needs the same guard. …

Affected
PackageRegistryAffectedFixed in
flowisenpm<= 3.1.33.1.4
flowise-componentsnpm<= 3.1.33.1.4

The impact, patch and workaround text comes from the advisory, shortened (published by Flowise). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].