Langflow <= 1.6.9 CORS Misconfiguration to Token Hijack & RCE
Exploited in the wild, in CISA KEV since 21 May 2026 (due 4 Jun 2026), with 3 public exploits. No fixed version is recorded.
Langflow versions up to and including 1.6.9 contain a chained vulnerability that enables account takeover and remote code execution. An overly permissive CORS configuration (allow_origins='*' with allow_credentials=True) combined with a refresh token cookie configured as SameSite=None allows a malicious webpage to perform cross-origin requests that include credentials and successfully call the refresh endpoint. An attacker-controlled origin can therefore obtain fresh access_token / refresh_token pairs for a victim session. Obtained tokens permit access to authenticated endpoints — including built-in code-execution functionality — allowing the attacker to execute arbitrary code and achieve full system compromise.
Briefing
Written from the sources below · deepseek-v4.1-flash
Langflow up to and including 1.6.9 chains a permissive CORS configuration (allow_origins='*' with credentials) and a SameSite=None refresh token cookie, letting a malicious webpage obtain victim token pairs. The tokens allow access to authenticated, code-execution endpoints, enabling account takeover and remote code execution.
Why it mattersIt is in CISA KEV with confirmed exploitation, public exploit material (nuclei, writeup) and EPSS of 93%, so exposed Langflow instances face imminent compromise.
ActionUpgrade Langflow to a version after 1.6.9; if unavailable, restrict CORS origins and set the refresh cookie SameSite to prevent cross-origin credential requests.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Langflow | Langflow | <=1.6.9 |
Exploit evidence
3 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