Critical (9.3) in Langflow Langflow. In CISA KEV since 2026-03-25. EPSS 97% estimated probability of exploitation activity in the next 30 days. Fixed in langflow 1.9.0.
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.
97%(unchanged from 96% a week ago; 25% 30 days ago) estimated probability of exploitation activity in the next 30 days; 100th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA KEV
listed 2026-03-25, due 2026-04-08
CISA's assessment (SSVC)
Exploitation: active · Automatable: yes · Technical impact: total, assessed 2026-03-26. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-94Improper Control of Generation of Code (Code Injection) CWE-95Improper Neutralization of Directives in Dynamically Evaluated Code (Eval Injection) CWE-306Missing Authentication for Critical Functionality
Show the promptExplain CVE-2026-33017 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-33017?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-33017?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-33017 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.
Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.
MaxMnMl/langflow-CVE-2026-33017-pocHarbor Check: matches CVE10 stars, Python, created CVE-2026-33017 - An unauthenticated remote code execution in Langflow <= 1.8.1 via Public Flow Build Endpoint
z4yd3/PoC-CVE-2026-33017Harbor Check: matches CVE5 stars, Python, created CVE-2026-33017: Unauthenticated RCE in Langflow
CerberusMrXi/Langflow-cve-2026-33017-exploitHarbor Check: matches CVE2 stars, Python, created CVE-2026-33017 exploitation tool for Langflow <1.9.0. Features reverse shells, command execution, file operations, persistence, and automat…
c0gnit00/CVE-2026-33017Harbor Check: matches CVE2 stars, Python, created Python POC, Exploit for CVE-2026-33017
21 more
MaximilianoMeyer/CVE-2026-33017Harbor Check: matches CVE1 star, Python, created Simple Proof Of Concept about CVE 2026-33017
omer-efe-curkus/CVE-2026-33017-Langflow-RCE-PoCHarbor Check: matches CVE1 star, Python, created The vulnerability in Langflow 1.8.1 and earlier allows a remote, unauthenticated attacker to achieve arbitrary command execution on the hos…
Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.