Authenticated code execution via unsanitized upload filenames
Published Apr 30, 2026 · Updated Apr 30, 2026
Path traversal in IBM Langflow Desktop 1.2.0 through 1.8.4 allows remote authenticated users to write arbitrary files via the v2 API. The POST /api/v2/files/ endpoint passes unsanitized multipart filenames containing dot-dot sequences to local storage path handling. Valid credentials and network access to the backend are required; a crafted upload can overwrite host files and execute code with backend privileges.
Summary
What happened
Path traversal in IBM Langflow Desktop 1.2.0 through 1.8.4 allows remote authenticated users to write arbitrary files via the v2 API. The POST /api/v2/files/ endpoint passes unsanitized multipart filenames containing dot-dot sequences to local storage path handling. Valid credentials and network access to the backend are required; a crafted upload can overwrite host files and execute code with backend privileges.
The record
- CVE
- CVE-2026-4502
- Published
- Apr 30, 2026
- Updated
- Apr 30, 2026
- Vendor
- OpenBMC Project
- Product
- Langflow Desktop
- Classifications
- CWE-22, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 30, 2026CVE publishedPublication date reported by the CVE source.
- Apr 30, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.2.0 <=1.8.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo