Quick answers
- Is CVE-2026-48520 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-48520 being exploited in the wild.
- How severe is CVE-2026-48520?
- Medium severity, with a CVSS score of 6.1, published 23 June 2026.
- Which products and versions are affected?
- langflow (PyPI) ECOSYSTEM:introduced=0,fixed=1.10.0.
- Is there a fix for CVE-2026-48520?
- Yes. langflow (PyPI): upgrade to 1.10.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-48520 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-48520?
- Check whether you run langflow (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- langflow (PyPI): upgrade to 1.10.0 or later
pip install "langflow>=1.10.0"
Technical details
An arbitrary file-read vulnerability exists in Langflow's "Shareable Playground" (Public Flows) feature due to improper validation of user-supplied file paths. The vulnerability is rooted in the `/api/v1/build_public_tmp` endpoint, where the `files` field in the execution request is processed by `LCModelComponent._get_chat_result` and `to_lc_message`. An unauthenticated attacker can provide arbitrary local filesystem paths or S3 URIs, which the application then reads and feeds into the Large Language Model (LLM) as input. Depending on the LLM's configuration and the flow's design, the contents of these files can be exfiltrated. This issue is classified as CWE-73 (External Control of File Name or Path) and is resolved in version 1.10.0.
Affected products
- langflow-ai Langflow < 1.10.0
Identifiers
- CVE-2026-48520
- GHSA-rcjh-r59h-gq37
- PYSEC-2026-244
Timeline
- 2026-06-09: advisory: GitHub Security Advisory published
- 2026-06-23: disclosed: CVE published to NVD