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.
The application is configured with an overly permissive CORS policy (allow_origins='*' with allow_credentials=True), which is an incorrect combination — the browser should block such requests, however an implementation error enables their execution. At the same time, the refresh token cookie is configured with the SameSite=None flag, which allows a malicious website to send cross-origin requests containing credentials. An attacker can trick a victim into visiting a website controlled by the attacker, which calls the token refresh endpoint, thereby obtaining access_token / refresh_token pairs for the victim's session. The obtained tokens enable access to authenticated endpoints, including the built-in code execution functionality, leading to the execution of arbitrary code on the server.
An attacker can hijack the session of an authenticated user and then leverage the code execution mechanisms built into Langflow to execute arbitrary commands on the server and achieve full system compromise (complete control over the server and potentially over connected resources).
Apply patches available from the vendor according to the references. As a workaround, it is recommended to immediately correct the CORS configuration — remove the combination of allow_origins='*' with allow_credentials=True — and change the SameSite flag for the refresh token cookie to Strict or Lax.
Langflow versions up to and including 1.6.9 (Langflow-ai/Langflow)
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/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:XLangflow
APPLangflow≤ 1.6.9
CISA KEV — detailsi
- Vendori
- Langflow
- Producti
- Langflow
- Added to KEVi
- May 21, 2026
- Remediation deadline (US Federal)i
- June 4, 2026(overdue)
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 contains an origin validation error vulnerability in which an overly permissive CORS configuration 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. This could allow the attacker to execute arbitrary code and achieve full system compromise via obtained tokens that permit access to authenticated endpoints.
Related vulnerabilities
IBM Langflow OSS: RCE przez nieuprawniony dostęp do tokenów SUPERUSER
Langflow: nieuwierzytelniony RCE przez endpoint budowania publicznych przepływów
Langflow RCE przez parametr exec_globals w endpoincie validate
Nieuwierzytelnione RCE w Langflow poprzez wstrzyknięcie kodu w endpoint /api/v1/validate/code
IBM Langflow OSS 1.0.0 through 1.11.1 could allow a remote attacker to execute arbitrary code due to improper ...