CVE-2026-91935: Flowise before 3.1.4 SSRF and API Key Exfiltration via Chat Model Nodes

Published Sep 15, 2026
·
Updated

Flowise before 3.1.4 fails to validate baseURL parameters in chat-model nodes, allowing authenticated users to redirect requests to arbitrary hosts. Attackers with chatflows:create or chatflows:update permissions can exfiltrate LLM provider API keys by redirecting requests to cloud metadata services or internal hosts.

Affected Software

1 affected component
Flowise<3.1.4

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Flowise to a version that resolves this vulnerability.

    Fixed in 3.1.4
  2. Configuration

    Upgrade to a version with SSRF protection (Flowise before 3.1.4 does not validate baseURL in chat-model nodes), so baseURL parameters cannot be used to redirect requests to cloud metadata services or internal hosts.

    Flowise chat-model nodes baseURL parameter validation = validate baseURL to prevent redirects to arbitrary hosts (SSRF)

Event History

Sep 15, 2026
CVE Published
via MITRE·03:17 PM
Data Sourced
via MITRE·03:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who can exploit this issue?

An authenticated Flowise user with either chatflows:create or chatflows:update permission can exploit it. The issue is exposed through chat-model nodes that accept a baseURL parameter.

2

What can an attacker do with successful exploitation?

An attacker can cause Flowise to send requests to arbitrary hosts, including internal services or cloud metadata endpoints. This can be used to exfiltrate LLM provider API keys.

3

Which versions are affected?

Flowise versions before 3.1.4 are affected. Upgrading to 3.1.4 or later addresses the affected version range described here.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203