Patchfirst
CVE-2025-34291 KEVPublic exploit High · 8.8 EPSS 92.8%

Langflow Origin Validation Error Vulnerability

Langflow · Langflow

Summary

Langflow versions up to and including 1.6.9 contain an origin validation flaw, stemming from an overly permissive CORS configuration combined with a SameSite=None refresh token cookie, that lets cross-origin requests from a malicious webpage carry credentials. An attacker who can get a victim to load a page they control, with the victim's Langflow session active, can obtain fresh access and refresh tokens and use them to reach authenticated endpoints, including built-in code-execution functionality, to run arbitrary code on the system.

Official description · NVD

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.

Breakdown
78.0 / 100
Exploited
Yes, in CISA KEV
Reports
1
Tactics
2/15

How an attack unfolds

Based on mappings. Select a step to see the evidence.
  1. How attackers get in

  2. What they do

First seen exploited 49 days after disclosure. Public exploit code (PoC-in-GitHub) appeared 5 months after disclosure.

  1. Disclosedday 0
  2. First seen exploitedVulnCheck KEV evidence+49 days
  3. Named in a threat reportctrlaltintel.com+3 mo
  4. Public exploit codePoC-in-GitHub+5 mo
  5. Added to CISA KEVEU database agrees+5 mo

CISA KEV listing is when exploitation was confirmed, not necessarily the first attack.

7 fixes in langflow over 15 months. The latest fix listed for langflow is 1.7.1.

Fixes in langflowPyPI package, by fixed version. Earlier and later fixes in the same package, not necessarily the same bug.

  1. 1.3.0CVE-2025-32487 Apr 2025KEV
  2. 1.5.1CVE-2025-5776025 Aug 2025
  3. 1.5.1CVE-2026-3404627 Mar 2026
  4. 1.7.0CVE-2025-342915 Dec 2025KEV
  5. 1.7.0CVE-2026-5542323 Jun 2026
  6. 1.7.1CVE-2025-6847719 Dec 2025
  7. 1.7.1CVE-2025-6847819 Dec 2025Latest listed

techniques

2 , grouped by in kill-chain order, 2 cited passages 2

Initial AccessTA0001

Exploit Public-Facing Application T1190 Medium
AI mapping from the description · how it is exploited

Cross-origin web request exploits exposed application endpoint

An attacker-controlled origin can therefore obtain fresh access_token / refresh_token pairs for a victim session
From the official description (NVD) Original (opens in a new tab) ↗

ExecutionTA0002

Command and Scripting Interpreter T1059 Medium
AI mapping from the description · primary impact

Built-in code execution functionality yields arbitrary command execution

allowing the attacker to execute arbitrary code and achieve full system compromise
From the official description (NVD) Original (opens in a new tab) ↗

Detection

0 rules for this CVE · 244 general rules for its techniques

Rules for this CVE

0 that reference CVE-2025-34291 directly.

CVE-specific rules are not available in this build. Search SigmaHQ ↗

Sigma rules © SigmaHQ, Detection Rule License 1.1; linked, not reproduced.

Am I affected? What do I upgrade to?

From GitHub Security Advisories and OSV

1 package in 1 ecosystem. Main package: langflow.

Upgrade to 1.10.3 or later

Fixes this CVE and 12 other known vulnerabilities in this package (CVE-2024-37014, CVE-2025-3248, +10).

pippip install "langflow>=1.10.3"

First fixed in 1.7.0 for CVE-2025-34291.

Affected versions

If you runUpgrade to
All versions before 1.7.01.10.3first fix for this CVE: 1.7.0

“Up to” means the second version is the fix and is not affected.

Check your lockfile against all CVEs

What security researchers reported

Named in 1 threat report
1 reportctrlaltintel.comMar 2026

Reports are matched by finding the exact id CVE-2025-34291 in their text; nobody has reviewed the match. One passage is shown per report, at most 320 characters, linked to the original.

Also mentioned in 50 community threat pulses (AlienVault OTX)

Weaker evidence

Pulses are indicator collections that anyone can publish. A mention is not confirmation of exploitation.

References

5 links, grouped by NVD tag
↑ ↓ chooseEnter openEsc close