Threats / Langflow / CVE-2026-33017
CVE-2026-33017
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Langflow vulnerability
Langflow contains a code injection vulnerability allowing unauthenticated construction of public flows, enabling arbitrary code execution without proper access controls.
Verdict
Today item — known-exploited.
An unauthenticated attacker can inject and execute arbitrary code through Langflow's public flow builder, bypassing authentication mechanisms. This vulnerability is actively exploited in the wild and poses significant risk to deployed instances.
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
9 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2026-03-25).
Probability (EPSS)
EPSS 0.98412 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Langflow, Langflow. Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-94 Code Injection, CWE-95 Eval Injection, CWE-306 Missing Authentication — weakness family: Injection, Authentication.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
WeaknessCWE-94 · Code InjectionCWE-95 · Eval InjectionCWE-306 · Missing AuthenticationInjection, Authentication
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I identify that Langflow's public flow endpoint lacks authentication enforcement on code injection points.
Business
Attackers gain unrestricted code execution capability on production systems without credentials.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I craft malicious flow definitions containing injected code that executes during flow processing.
Business
Arbitrary code runs with the privileges of the Langflow application, compromising data and system integrity.
3
Lateral reach — past segmentation narrative 3
Attacker
I establish persistence or lateral movement by leveraging code execution to access underlying infrastructure.
Business
Breach scope expands beyond Langflow to connected systems, databases, and organizational networks.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05