The 'POST /api/v2/files' endpoint does not sanitize the 'filename' parameter from the multipart form data, allowing an attacker to write files to arbitrary locations on the filesystem using path traversal sequences ('../').
CVE-2026-5027
Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-03-27. the CNA's CVSS baseline 8.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.8
- EG Score
- 8.8(medium)
- EG Risk
- 40(Track)EG Risk 40/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity88% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 31%
- EPSS %ILE
- 98%
- KEV
- Not listed
Published
March 27, 2026
Last Modified
June 17, 2026
Advisory Details (1)
Auto-updated Jul 28, 2026Langflow - Path Traversal Arbitrary File Write via upload_user_file - Research Advisory | Tenable®
https://www.tenable.com/security/research/tra-2026-26Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 8× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-30 16:28 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-28 15:37 UTCEPSS rescore
- 2026-07-27 14:14 UTCEPSS rescore
- 2026-07-27 12:50 UTCEG score recompute
- 2026-07-27 12:50 UTCGHSA enrichment
Publicly available exploits
(2 references)Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- GitHub PoCEQSTLab/CVE-2026-5027First seen Apr 3, 2026
Langflow, Remote Code Execution (RCE) via Cron Job Injection through Path Traversal
Open source ↗ - Nucleihttp/cves/2026/CVE-2026-5027.yamlFirst seen Jan 1, 2026
Langflow <= 1.8.4 - Path Traversal to RCE via File Upload
Open source ↗
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-5027?
When was CVE-2026-5027 disclosed?
Is CVE-2026-5027 actively exploited?
What is the CVSS score of CVE-2026-5027?
How do I remediate CVE-2026-5027?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-5027
Is Your Infrastructure Affected by CVE-2026-5027?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.