Langflow has Unauthenticated Remote Code Execution via Public Flow Build Endpoint
Exploited in the wild, in CISA KEV since 25 Mar 2026 (due 8 Apr 2026), with 4 public exploits. No fixed version is recorded.
Langflow is a tool for building and deploying AI-powered agents and workflows. In versions prior to 1.9.0, the POST /api/v1/build_public_tmp/{flow_id}/flow endpoint allows building public flows without requiring authentication. When the optional data parameter is supplied, the endpoint uses attacker-controlled flow data (containing arbitrary Python code in node definitions) instead of the stored flow data from the database. This code is passed to exec() with zero sandboxing, resulting in unauthenticated remote code execution. This is distinct from CVE-2025-3248, which fixed /api/v1/validate/code by adding authentication. The build_public_tmp endpoint is designed to be unauthenticated (for public flows) but incorrectly accepts attacker-supplied flow data containing arbitrary executable code. This issue has been fixed in version 1.9.0.
Briefing
Written from the sources below · deepseek-v4.1-flash
Langflow versions prior to 1.9.0 let unauthenticated attackers build public flows with attacker-supplied data, executing arbitrary Python via exec() without sandboxing and achieving remote code execution. Langflow deployments exposing the public flow build endpoint are affected.
Why it mattersExploitation is confirmed and listed in CISA KEV, with public exploit code, a 96% EPSS score, and a CVSS of 9.3, so exposed instances face imminent risk.
ActionUpgrade to Langflow 1.9.0; if patching is blocked, restrict access to /api/v1/build_public_tmp/ endpoints.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Langflow | Langflow | ||
| langflow-ai | <1.9.0 |
Exploit evidence
4 public sources
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Langflow, strongest first
Embed
A live severity badge for an advisory, README or ticket