A critical information disclosure vulnerability in Flowise allows unauthenticated attackers to retrieve plaintext API keys and sensitive configuration data.

This vulnerability involves the improper exposure of sensitive information (CWE-200) through the GET /api/v1/public-chatflows/:id and public-chatbotConfig endpoints. The application fails to sanitize flow data, allowing unauthenticated actors to access credential IDs and plaintext secrets intended for internal use.

The exposure of API keys and password fields presents a severe risk to the confidentiality and integrity of connected services. An attacker gaining these credentials could pivot into integrated cloud platforms or LLM providers, leading to unauthorized data access, financial loss through service abuse, or complete compromise of downstream infrastructure. Given the CVSS score of 7.5, this high-severity flaw requires immediate attention to prevent unauthorized access to sensitive environment configurations.

Immediate Action: Update Flowise to version 3.1.0 or later immediately to apply the necessary sanitization logic to public endpoints.

Proactive Monitoring: Review API access logs for suspicious requests to the public-chatflows and public-chatbotConfig endpoints, particularly from unknown or unauthorized IP addresses.

Compensating Controls: Implement strict network access controls or a Web Application Firewall (WAF) to restrict access to the /api/v1/public-chatflows/ endpoint to trusted network segments until patching is complete.

Public Exploit Available: Unknown

This vulnerability represents a significant security oversight that exposes highly sensitive configuration data to the public internet. Organizations utilizing Flowise should prioritize upgrading to version 3.1.0 without delay to ensure that sensitive credentials are no longer returned by the public API. Failure to remediate this issue leaves the environment susceptible to credential theft and subsequent unauthorized lateral movement across integrated services.