CVE-2025-34291: Langflow Origin Validation Error
Langflow · listed in the CISA catalog of actively exploited vulnerabilities since 2026-05-21.
- CVSS v4.0 (CVE record)
- 9.4
- critical
- EPSS (exploit probability, 30 days)
- 93%
- higher than 99.8% of all CVEs
- Added to CISA KEV
- 2026-05-21
- US federal due date 2026-06-04
- Automatable (CISA SSVC)
- no
- technical impact: total
CVE-2025-34291 explained
CVE-2025-34291 is a chained origin validation flaw in Langflow versions up to and including 1.6.9. An overly permissive CORS setup and a refresh token cookie set to SameSite=None let a malicious webpage obtain fresh tokens for a victim's session. CISA lists it as known exploited, and it can lead to account takeover and full system compromise.
Impact
A malicious webpage can make credentialed cross-origin requests to the refresh endpoint and obtain new access and refresh tokens for a victim's session. With those tokens, an attacker can reach authenticated endpoints, including built-in code-execution functionality, and run arbitrary code. CISA rates the technical impact as total and the vulnerability as not automatable. Attackers are known to exploit it.
Who is affected
Langflow versions ≤ 1.6.9 are affected, according to the CVE record published by VulnCheck. The CVE record names no fixed version. Check the vendor advisory for the version that contains the fix and for mitigation guidance.
Written with AI from the data on this page and checked against it automatically.
Official description
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.
CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
CISA notes
- This vulnerability could affect an open-source component, third-party library, protocol, or proprietary implementation that could be used by different products. For more information, please see: github.com/langflow-ai/langflow
- github.com/langflow-ai/langflow/releases/tag/v1.9.3; github.com/langflow-ai/langflow/issues/11465
- nvd.nist.gov/vuln/detail/CVE-2025-34291
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- LangflowCORSMiddleware configuration, refresh token cookie handlingAffectedFixed in
- ≤ 1.6.9
not stated
| Product | Affected | Fixed in |
|---|---|---|
| LangflowCORSMiddleware configuration, refresh token cookie handling |
| not stated |
How to fix it
- The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
- Vendor advisory: github.com/langflow-ai/langflow/releases/tag/v1.9.3
- CISA's deadline for US federal agencies: 2026-06-04 (passed) – a useful benchmark for everyone else, too.
What to do
- Follow the Langflow vendor advisory and apply the fixed version or mitigations it names.
- Apply mitigations per vendor instructions, as CISA's required action states, or discontinue use if mitigations are unavailable.
- Restrict network access to Langflow instances and keep them off the public internet where possible.
- Revoke existing sessions and tokens and review logs for unexpected token refreshes or code execution.
- Check Langflow hosts for signs of compromise, given confirmed exploitation.
The CVE record names no fixed version. Check the Langflow vendor advisory for a fixed release or mitigations. CISA requires applying mitigations per vendor instructions, following BOD 22-01 guidance for cloud services, or discontinuing use of the product if mitigations are unavailable. Meanwhile, limit network exposure and monitor for signs of compromise.
Written with AI from the data on this page and checked against it automatically.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- No – each attack needs manual steps
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-346 Origin Validation Error
Questions about CVE-2025-34291
- Is CVE-2025-34291 being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2026-05-21, with a US federal due date of 2026-06-04. Known ransomware use is listed as unknown.
- Which Langflow versions are affected?
- Langflow versions
≤ 1.6.9are affected. The CVE record names no fixed version, so consult the vendor advisory for the fix. - What can an attacker achieve?
- By obtaining fresh tokens for a victim's session, an attacker can take over the account, use built-in code-execution functionality, run arbitrary code and fully compromise the system.
Written with AI from the data on this page and checked against it automatically.
References
Trackers and catalogs
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.