<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:webfeeds="http://webfeeds.org/rss/1.0"><channel><title>Cve-2025-34291 - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/cve-2025-34291/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Thu, 21 May 2026 18:58:51 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/cve-2025-34291/feed.xml" rel="self" type="application/rss+xml"/><image><url>https://feed.craftedsignal.io/favicon-32x32.png</url><title>CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/</link><width>32</width><height>32</height></image><webfeeds:icon>https://feed.craftedsignal.io/favicon.svg</webfeeds:icon><item><title>Langflow Origin Validation Error Vulnerability (CVE-2025-34291)</title><link>https://feed.craftedsignal.io/briefs/2026-05-langflow-cors/</link><pubDate>Thu, 21 May 2026 18:58:51 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-05-langflow-cors/</guid><description>Langflow contains an origin validation error vulnerability (CVE-2025-34291) due to an overly permissive CORS configuration combined with a refresh token cookie configured as SameSite=None, allowing malicious webpages to perform cross-origin requests and potentially leading to arbitrary code execution and full system compromise.</description><content:encoded><![CDATA[<h2 id="overview">Overview</h2>
<p>Langflow is vulnerable to an origin validation error (CVE-2025-34291) stemming from a misconfiguration of Cross-Origin Resource Sharing (CORS). This, combined with the use of a refresh token cookie lacking proper SameSite restrictions (SameSite=None), allows attackers to bypass standard browser security mechanisms.  A malicious actor can craft a webpage that, when visited by an authenticated Langflow user, can make unauthorized cross-origin requests to the Langflow server. This vulnerability allows an attacker to call the refresh endpoint and obtain tokens to access authenticated endpoints. The attacker can then leverage these tokens to perform actions as the compromised user, potentially leading to complete system compromise and data exfiltration. This vulnerability affects installations of Langflow prior to version 1.9.3.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Attacker identifies a Langflow instance with a vulnerable CORS configuration and SameSite=None refresh token cookie.</li>
<li>Attacker crafts a malicious webpage designed to exploit the CORS misconfiguration.</li>
<li>The attacker distributes the malicious webpage via phishing or other social engineering tactics.</li>
<li>Victim, an authenticated Langflow user, visits the malicious webpage.</li>
<li>The malicious webpage executes JavaScript code that initiates a cross-origin request to the Langflow server, including the refresh token cookie.</li>
<li>Due to the permissive CORS policy and missing SameSite attribute, the Langflow server processes the request and returns a valid access token to the malicious webpage.</li>
<li>The attacker uses the obtained access token to access authenticated endpoints on the Langflow server, performing actions as the compromised user.</li>
<li>The attacker leverages the compromised access to execute arbitrary code and gain full system compromise, potentially exfiltrating sensitive data.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of CVE-2025-34291 can lead to complete compromise of a Langflow installation. An attacker can gain unauthorized access to sensitive data, execute arbitrary code on the server, and potentially pivot to other systems within the network. The lack of proper origin validation makes Langflow instances highly susceptible to cross-site request forgery (CSRF) attacks, where authenticated users are tricked into performing actions without their knowledge or consent. This could affect any Langflow deployment, including cloud-based and on-premise installations.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Apply the mitigations as documented in the vendor advisory (<a href="https://github.com/langflow-ai/langflow">https://github.com/langflow-ai/langflow</a>).</li>
<li>Upgrade Langflow to version 1.9.3 or later, which addresses the CORS misconfiguration (<a href="https://github.com/langflow-ai/langflow/releases/tag/v1.9.3">https://github.com/langflow-ai/langflow/releases/tag/v1.9.3</a>).</li>
<li>Implement stricter CORS policies to restrict cross-origin requests to only trusted domains.</li>
<li>Configure refresh token cookies with the <code>SameSite=Strict</code> or <code>SameSite=Lax</code> attribute to prevent them from being sent with cross-origin requests.</li>
<li>Deploy the Sigma rule <code>Detect Langflow CVE-2025-34291 Exploitation Attempt via Malicious Referer</code> to identify potential exploitation attempts based on the Referer header.</li>
<li>Apply applicable BOD 22-01 guidance for cloud services as recommended by CISA.</li>
</ul>
]]></content:encoded><category domain="severity">critical</category><category domain="type">threat</category><category>cve-2025-34291</category><category>cors</category><category>csrf</category><category>langflow</category><category>cloud</category><category>origin validation</category></item></channel></rss>