FalehSec Exploited-vulnerability triage · joined from CISA KEV, NVD CVSS and EPSS

CVE-2026-33017

Langflow · Langflow · Langflow Code Injection Vulnerability

Verdict
Patch first · actively exploited, reachable from the internet without credentials, and in the top 1% of CVEs by near-term exploitation probability

Added to CISA KEV 2026-03-25 · exploited in the wild for 227 days

How a test catches it

Test
Trace every path by which a user-supplied string becomes executable - a script body, a template, a job definition, a workflow field - and submit a value that would fail to parse if it were evaluated.
Passes when
The value is treated as data at every point. One field that reaches an evaluator is the finding, and the other fields being safe does not offset it.
What an attacker can reach How likely Time What CISA says to do Sources All 566

What an attacker can reach

CVSS 9.3 CRITICAL. The score is a summary; these three components are the part that decides whether something scanning the internet can use it.

Attack vectornetworkreachable over the network, with no local access needed
Privileges requirednoneneeds no credentials at all
User interactionnonecan be triggered with nobody interacting with the page or request
Base vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
WeaknessCWE-94

This describes the vulnerability. It says nothing about whether your systems run it.

How likely

EPSS puts the probability of exploitation in the next 30 days at 0.9635, which places it in the top 1% of all tracked CVEs. The percentile is the more useful half: 0.18 in absolute terms sounds low until you know most of the internet-facing software in the world scores under that.

EPSS probability0.9635
Percentile0.999 — top 1%

Time

Added to KEV2026-03-25
Days exploited227
Federal remediation duenot set
Ransomware useno known ransomware campaign use

What CISA says to do

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

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.

Sources

This page describes the bug, not your estate. It cannot tell you whether you run it, or whether your own systems carry the same class of flaw. That question is what an assessment answers.

Web application penetration testing · API security testing · every service