What it is
CVE-2025-34291 is an unauthenticated Langflow <= 1.6.9 CORS Misconfiguration to Token Hijack & RCE. Langflow versions up to and including 1.6.9 contain a chained vulnerability that enables account takeover and remote...
Vulnerability report
Langflow <= 1.6.9 CORS Misconfiguration to Token Hijack & RCE
Langflow · 0 to <= 1.6.9
Decision summary
Direct answers before the deeper technical record.
What it is
CVE-2025-34291 is an unauthenticated Langflow <= 1.6.9 CORS Misconfiguration to Token Hijack & RCE. Langflow versions up to and including 1.6.9 contain a chained vulnerability that enables account takeover and remote...
Is it exploited?
Yes. Previdian tracks this CVE as a known exploited vulnerability. Confidence is confirmed. Listed in CISA KEV. Also confirmed by third-party sources.
Who is affected?
Langflow 0 to <= 1.6.9.
What should we do?
Prioritize remediation. Validate affected assets and apply vendor fixes on an accelerated timeline.
Overview
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.
Exploitation evidence
Third-party attestation and first-party sensor observation are shown separately so teams can judge the evidence chain.
CVE
A trusted third party reported exploitation.
Nuclei Templates
Public scanner or PoC coverage increases practical exploitability.
Per-source evidence links for KEV attestations are available through the Previdian Pro API.
Learn about Pro API access| Source | Added |
|---|---|
| CVE First | 2026-06-01 13:29 UTC |
| CISA | 2026-06-02 14:00 UTC |
Detection
Make the evidence actionable in scanner, SOC, and edge-control workflows.
Request targets and User-Agents available in Pro. Callback host details available in Enterprise.
Nuclei template detected 01 Jun 2026.
View Nuclei template (opens in new tab)No Previdian virtual patch is currently available. Future rules ship for ModSecurity, Cloudflare, and AWS WAF.
Learn about virtual patches →Scanner and exploit-framework references linked to this CVE.
| Scanner | Reference | Detected |
|---|---|---|
| Nuclei | https://github.com/projectdiscovery/nuclei-templates/blob/main/http/cves/2025/CVE-2025-34291.yaml | 01 Jun 2026 |
Risk and context
CVSS v4.0
Potential damage if exploited. Separate from whether attackers are using it.
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
EPSS
92.8%
Estimated chance of exploitation in the next 30 days. Previdian's warning comes from evidence, not this score.
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
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
These PoCs are unverified and could contain malware. Use at your own risk.
cve · Created Unknown
nuclei · Created Unknown
Timeline
14:21 UTC
Public proof-of-concept code published
14:00 UTC
Listed in the CISA Known Exploited Vulnerabilities catalog
15:34 UTC
Scanner coverage available
13:29 UTC
High-confidence, third-party attested exploitation
22:27 UTC
Vulnerability disclosed publicly
19:15 UTC
Identifier reserved by the CNA
Pro API
Confidence, exploit status, sensor telemetry, PoCs, scanner integrations, mentions, and tags are available programmatically for VM, SOC, and CTI workflows.
GET /api/v2/pro/kevs/CVE-2025-34291
Sample API response{
"cve_id": "CVE-2025-34291",
"confidence": "Confirmed",
"cvss_score": 9.4,
"cvss_estimated": false,
"epss_score": 0.92808,
"exploit_status": {
"exploited_in_the_wild": true,
"active_exploitation_observed": false
},
"sensor_telemetry": { "attempts": 0, "sensors": 0 }
}