Langflow CORS misconfiguration enables Account Takeover and RCEGHSA-577h-p2hh-v4mv
HIGHFix: langflow-ai/langflow#10139GHSA-577h-p2hh-v4mv is a high-severity (CVSS 8.8) CWE-346 vulnerability in langflow. It is in CISA's Known Exploited Vulnerabilities catalog (added 2026-05-21) — treat it as actively exploited and patch now. A fix is available for langflow — see the affected versions and patch details below.
Exploitation Status
Actively exploited in the wild
- Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2026-05-21. Federal agencies were required to remediate by 2026-06-04.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA (KEV catalog and SSVC triage) for GHSA-577h-p2hh-v4mv.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-577h-p2hh-v4mv by exploitation likelihood (EPSS) against impact (CVSS). In the shaded patch-first corner (EPSS 50%+, CVSS 7.0+).
Where this sits among everything scored
Of 395,249 CVEs with a current EPSS score, this one falls in the ≥ 90% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
langflowReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | langflow | all versions | 1.7.0pip install --upgrade 'langflow==1.7.0' |
Affected Products
langflowlangflowDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for langflow, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update langflow to 1.7.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-577h-p2hh-v4mv is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How to detect GHSA-577h-p2hh-v4mv
A community-maintained Nuclei template exists for this CVE. You can scan for it directly:
nuclei -id ghsa-577h-p2hh-v4mv -u https://target- Template
- Langflow AI <= 1.6.9 - CORS Misconfiguration
- Severity
- critical
- Impact
- An attacker can steal authentication tokens via CORS and execute arbitrary code on the server.
- Remediation
- Upgrade to Langflow version 1.7.0 or later which restricts CORS origins properly.
Template by ProjectDiscovery nuclei-templates (686f6c61), MIT licensed. View the full template. Scan only systems you are authorised to test.
Frequently Asked Questions
Is GHSA-577h-p2hh-v4mv in your dependencies?
Find it across PyPI, including transitive dependencies.