Unauthenticated file read via public flow paths
Published Jun 23, 2026 · Updated Jun 23, 2026
Arbitrary file read in Langflow OSS before 1.10.0 allows remote attackers to read local or S3 files through a public flow request. The /api/v1/build_public_tmp route accepts attacker-controlled entries in its files field, and LCModelComponent._get_chat_result passes them to to_lc_message for storage-backed reads into the configured LLM. Exploitation requires a shared public flow and a compatible LLM configuration; the consequence is limited to file confidentiality.
Summary
What happened
Arbitrary file read in Langflow OSS before 1.10.0 allows remote attackers to read local or S3 files through a public flow request. The /api/v1/build_public_tmp route accepts attacker-controlled entries in its files field, and LCModelComponent._get_chat_result passes them to to_lc_message for storage-backed reads into the configured LLM. Exploitation requires a shared public flow and a compatible LLM configuration; the consequence is limited to file confidentiality.
The record
- CVE
- CVE-2026-48520
- Published
- Jun 23, 2026
- Updated
- Jun 23, 2026
- Vendor
- OpenBMC Project
- Product
- Langflow OSS
- Classifications
- CWE-73, T1005, T1530, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 23, 2026CVE publishedPublication date reported by the CVE source.
- Jun 23, 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.10.0
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
- Langflow public-flow file-read reproductionproof of concept · demonstrated
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