CVE-2024-8181: Flowiseai Flowise Auth Bypass Vulnerability

CVE-2024-8181 Overview

CVE-2024-8181 is an authentication bypass vulnerability in Flowise version 1.8.2, an open-source low-code tool for building customized large language model (LLM) orchestration flows. The flaw allows a remote, unauthenticated attacker to reach API endpoints as if they were an administrator. Successful exploitation grants access to restricted functionality without supplying valid credentials. The vulnerability is tracked under CWE-287: Improper Authentication and was disclosed by Tenable in advisory TRA-2024-33.

Critical Impact

Unauthenticated remote attackers can invoke administrator-only API endpoints in Flowise 1.8.2, exposing LLM flows, credentials, and configuration data.

Affected Products

• Flowiseai Flowise version 1.8.2
• Self-hosted Flowise deployments exposing the HTTP API
• Containerized Flowise instances reachable over the network

Discovery Timeline

• 2024-08-27 - CVE-2024-8181 published to NVD
• 2024-09-06 - Last updated in NVD database

Technical Details for CVE-2024-8181

Vulnerability Analysis

Flowise exposes a REST API used by both the web UI and external integrations to manage chatflows, credentials, API keys, and tool configurations. In version 1.8.2, the server-side middleware that enforces authentication on these routes does not consistently validate the caller. As a result, requests that should require an administrator session can be processed without one.

An attacker who can reach the Flowise HTTP port can invoke administrative endpoints directly. This includes endpoints that read or modify chatflows, retrieve stored credentials for downstream services (such as model providers and vector databases), and manage API keys. Because Flowise stores third-party secrets to drive its LLM pipelines, the bypass turns a single exposed instance into a pivot point against connected systems.

The issue is described in the Tenable Security Research Advisory.

Root Cause

The root cause is improper authentication enforcement on protected API routes [CWE-287]. The middleware responsible for verifying administrative identity does not reject anonymous requests on all sensitive endpoints, so the authorization check that follows operates on an unauthenticated context.

Attack Vector

The attack vector is network based and requires no privileges. An attacker sends crafted HTTP requests to the Flowise API and receives administrator-level responses. No valid session, token, or API key is needed to reach the affected endpoints in version 1.8.2.

No verified public exploit code is available for CVE-2024-8181.
Refer to the Tenable advisory (TRA-2024-33) for technical details
on the affected endpoints and request patterns.

Detection Methods for CVE-2024-8181

Indicators of Compromise

• Unauthenticated HTTP requests to Flowise administrative API paths such as /api/v1/chatflows, /api/v1/credentials, and /api/v1/apikey.
• Unexpected creation, modification, or export of chatflows and credentials in Flowise audit logs.
• Outbound requests from the Flowise host to attacker-controlled domains shortly after API activity.
• New or unknown API keys appearing in the Flowise configuration.

Detection Strategies

• Inspect web server and reverse proxy logs for requests to /api/v1/* Flowise endpoints that lack Authorization headers or session cookies and return 2xx responses.
• Correlate Flowise application logs with network telemetry to identify administrative actions performed from external IP addresses.
• Alert on credential or chatflow read operations that occur outside known maintenance windows or from non-corporate networks.

Monitoring Recommendations

• Forward Flowise application and access logs to a centralized analytics platform such as Singularity Data Lake for retention and correlation with endpoint telemetry.
• Track egress connections from the Flowise host, since exposed credentials can be used to call connected LLM providers and databases.
• Monitor for changes to the Flowise process, container image, or configuration files that may indicate post-exploitation persistence.

How to Mitigate CVE-2024-8181

Immediate Actions Required

• Upgrade Flowise to a version newer than 1.8.2 that addresses the authentication bypass.
• Remove direct internet exposure of the Flowise UI and API; place the service behind a VPN or authenticated reverse proxy.
• Rotate all credentials, API keys, and secrets configured in Flowise, since they may have been retrieved by unauthenticated callers.
• Review chatflows, tools, and API keys for unauthorized additions or modifications.

Patch Information

No vendor advisory URL is recorded in the NVD entry. Consult the project's release notes and the Tenable Security Research Advisory to identify a fixed release and upgrade from 1.8.2 accordingly.

Workarounds

• Restrict network access to the Flowise port using host firewalls, security groups, or Kubernetes network policies so that only trusted clients can reach the API.
• Front Flowise with an authenticating reverse proxy (for example, an OAuth2 or mTLS proxy) that rejects unauthenticated requests before they reach the application.
• Disable or remove Flowise instances that are not actively required, particularly any internet-facing deployments.

# Example: restrict Flowise (default port 3000) to a single management subnet using iptables
iptables -A INPUT -p tcp --dport 3000 -s 10.10.0.0/24 -j ACCEPT
iptables -A INPUT -p tcp --dport 3000 -j DROP