Skip to content
Threat Brief

← All advisories

CVE-2026-33017

Critical 9.3KEV · exploitedPublic exploitFix available

Langflow has Unauthenticated Remote Code Execution via Public Flow Build Endpoint

Record last updated

CVSS score

9.3

Critical on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

97%

Among the highest-scored CVEs. A prediction, not evidence.

CISA remediation deadline

227days overdue

Passed 227 days ago for U.S. federal agencies

Description

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.

Weakness: CWE-94, CWE-95, CWE-306

Patching and mitigation

Patch status
Fix available (source: CVE record (GitHub_M))
Fix documented (source date)
Mitigation
None documented
Vendor guidance
github.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
LangflowLangflowNot documentedNot documentedCISA KEV
langflow-ailangflow< 1.9.0Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by GitHub_M

    Source: CVE Program (opens in a new tab)

  2. 25 Mar 2026KEV

    Added to the CISA Known Exploited Vulnerabilities catalog

    Source: CISA KEV (opens in a new tab)

  3. 25 Mar 2026Exploitation

    Exploitation confirmed by CISA KEV

    Source: CISA KEV (opens in a new tab)

  4. Patch

    Fix documented by CVE record (GitHub_M)

    Source: CVE record (GitHub_M) (opens in a new tab)

Vendor guidance and references

Public exploit code

Exploit or proof-of-concept code is publicly available on Exploit-DB. Shown as a prioritization and defensive-testing signal — treat exploit code as hostile and run it only against systems you are authorized to test.