Langflow: Unauthenticated Shareable Playground arbitrary local or S3 file read

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.1 · CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:N/A:N

EPSS

• CVE-2026-48520: 0.44% estimated exploitation activity in the next 30 days; percentile 38.05 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary The "Shareable Playground" (or "Public Flows" in code) contains a potential arbitrary file-read vulnerability, depending on the exact flow configuration used. By making a flow public, public execution of the flow is allowed. The execution request can contain a list of files that gets read by Langflow and fed into the LLM. The files path can be any path supported by the storage - it can be either a local file or S3 path if supported by the local configuration Details Shareable Playground feature works by enabling the execution of workflows by unauthenticated users, by accessing a link. Specifically, it enables the route /api/v1/buildpublictmp to execute any public flow, given a public flow ID. This request contains a files field that can contain a list of files. The files get read in LCModelComponent.getchatresult in a call to tolcmessage. A detailed stacktrace: This triggers Langflow to feed the file into the LLM as an Image. Reading the files back depends on the specific LLM…

Published by the source

16 Jun 2026, 17:36 UTC

Last modified by the source

20 Jul 2026, 14:00 UTC

Source last checked

26 Oct 2026, 13:49 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-rcjh-r59h-gq37

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-rcjh-r59h-gq37

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-48520

Advisory: Langflow: Unauthenticated Shareable Playground arbitrary local or S3 file read
IDs: CVE-2026-48520, GHSA-rcjh-r59h-gq37
Record: https://patchnext.com/advisories/cve-2026-48520 (revision 2, source checked 26 Oct 2026, 13:49 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: langflow 1.10.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI langflow: affected < 1.10.0; fixed in 1.10.0

## Suggested inspection (read-only)
- `python -m pip show langflow`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on langflow.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-rcjh-r59h-gq37 (OSV record GHSA-rcjh-r59h-gq37 lists affected ranges: PyPI langflow >=0 <1.10.0 (fixed))
- Verified: https://github.com/advisories/GHSA-rcjh-r59h-gq37 (GitHub-reviewed advisory GHSA-rcjh-r59h-gq37 lists affected ranges: PyPI langflow >=0 <1.10.0)

Commands are suggestions: review each one before running it.