# CVE-2026-48519: Langflow: Unauthenticated RCE in Shareable Playgrounds

> Unauthenticated attackers can execute arbitrary Python code via the Shareable Playground feature in Langflow.

- **Severity:** Critical 9.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 23 Jun 2026
- **Updated:** 24 Jun 2026
- **Also known as:** GHSA-v5ff-9q35-q26f, PYSEC-2026-243

## What is CVE-2026-48519?

CVE-2026-48519 is a critical code injection vulnerability in Langflow Langflow, published on 23 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Langflow is a tool for building and deploying AI-powered agents and workflows. Prior to 1.9.2, the "Shareable Playground" (or "Public Flows" in code) contains a critical RCE vulnerability. Shareable Playground feature works by enabling the execution of workflows by unauthenticated users, by accessing a link. Specifically, it enables the route /api/v1/build_public_tmp to execute any public flow, given a public flow ID. When the route executes the flow, it allows for providing arbitrary custom Python code as the nodes code, inside the JSON payload. The vulnerable field is data.nodes[X].data.node.template.code.value. This vulnerability is fixed in 1.9.2.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2026-48519?

3 open source packages ship an affected version, including langflow. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `langflow` | PyPI | All versions | 1.9.2 |
| `langflow` | PyPI | All versions | 1.9.2 |
| `langflow` | PyPI | All versions | 1.9.2 |

Products: Langflow Langflow.

## How do I fix CVE-2026-48519?

Upgrade langflow to 1.9.2 or later.

## Is CVE-2026-48519 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-48519 exists.

Public exploit code:

- CVE-2026-48519 pre-auth rce poc in IBM langflow <= 1.9.1 (github_poc): https://github.com/lukehebe/IBM-Langflow-CVE-2026-48519-poc

## Other vulnerabilities in Langflow Langflow

- [CVE-2026-9198](https://insights.sbomify.com/CVE-2026-9198/): IBM Langflow Code Injection (critical 9.8, exploited in the wild)
- [CVE-2026-0770](https://insights.sbomify.com/CVE-2026-0770/): Langflow Inclusion of Functionality from Untrusted Control Sphere (critical 9.8, exploited in the wild)
- [CVE-2025-3248](https://insights.sbomify.com/CVE-2025-3248/): Langflow Missing Authentication (critical 9.8, exploited in the wild)
- [CVE-2025-34291](https://insights.sbomify.com/CVE-2025-34291/): Langflow Origin Validation Error (critical 9.4, exploited in the wild)
- [CVE-2026-33017](https://insights.sbomify.com/CVE-2026-33017/): Langflow Code Injection (critical 9.3, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-48519 and fix it if it is affected.

What it is: CVE-2026-48519 is a critical code injection vulnerability in Langflow Langflow, published on 23 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-48519 exists.

Affected packages and fixed versions:
- langflow (PyPI): affected all versions; fixed in 1.9.2
- langflow (PyPI): affected all versions; fixed in 1.9.2
- langflow (PyPI): affected all versions; fixed in 1.9.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-48519/ (Markdown: https://insights.sbomify.com/CVE-2026-48519/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-48519
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-48519
- OSV: https://osv.dev/vulnerability/CVE-2026-48519

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-48519/
Summaries are generated and may contain mistakes; the official description above is the record.