Skip to main content
Mallory
CriticalCISA KEVExploited in the wildPublic exploit

Langflow chained account takeover and RCE via CORS origin validation error

IdentifiersCVE-2025-34291CWE-346· Origin Validation Error

CVE-2025-34291 is a critical chained vulnerability in Langflow affecting versions up to and including 1.6.9. The issue arises from an overly permissive CORS configuration that allows credentialed cross-origin requests (e.g., allow_origins='*' with allow_credentials=True), combined with a refresh token cookie configured as SameSite=None and a refresh endpoint that can be invoked cross-origin. A malicious website visited by an authenticated Langflow user can cause the victim’s browser to send credentialed requests to the Langflow refresh endpoint and obtain fresh access_token and refresh_token pairs for the victim session. Those tokens can then be used to access authenticated Langflow endpoints, including built-in code-execution functionality such as the code validation path, resulting in account takeover and remote code execution on the host running Langflow. The chain effectively turns a browser-based cross-origin token theft condition into full server compromise.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an attacker to hijack an authenticated Langflow session, mint fresh authentication tokens, access authenticated application functionality, and execute arbitrary code through Langflow’s built-in code-execution features. This can lead to full system compromise of the Langflow host. Because Langflow commonly stores workflow secrets, API keys, database credentials, and service tokens, compromise may also expose sensitive stored credentials and enable downstream compromise of connected SaaS, cloud, database, and internal services. Public reporting and KEV inclusion indicate active exploitation in the wild.

Mitigation

If you can’t patch tonight, do this now.

If immediate upgrading is not possible, reduce exposure by restricting Langflow access to trusted networks and origins, disabling or tightly constraining credentialed cross-origin requests, and setting explicit CORS origin allowlists. Reconfigure authentication cookies to use stricter SameSite settings such as Lax or Strict where compatible. Monitor for suspicious cross-origin requests to refresh endpoints, anomalous token issuance, and unexpected use of code-execution-related endpoints. Consider removing internet exposure or discontinuing use of vulnerable instances until patched.

Remediation

Patch, then assume compromise.

Upgrade Langflow to version 1.7.0 or later. In addition, configure CORS to allow only explicitly trusted origins rather than wildcard origins, and ensure sensitive authentication cookies are not configured with SameSite=None unless strictly required. Where applicable, add or enforce CSRF protections and strict origin validation on token refresh flows. For potentially compromised or previously exposed instances, audit and rotate stored API keys, tokens, and other secrets accessible from the Langflow workspace.
PUBLIC EXPLOITS

Exploits

No valid public exploits. Mallory filtered out 2 candidates as fakes, detection scripts, or README-only repos.

VALID 0 / 2 TOTALView more in app

All candidate exploits were filtered out by Mallory's validation.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
LangflowLangflowapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

50 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence6

Every observed campaign linking this CVE to a named adversary.

Associated malware2

Malware families riding this exploit, with evidence and IOCs.

Detection signatures2

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity37

Community discussion across Reddit, Mastodon, and other social sources.