Quick answers
- Is CVE-2026-48519 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-48519 being exploited in the wild.
- How severe is CVE-2026-48519?
- Critical severity, with a CVSS score of 9.6, published 23 June 2026.
- Which products and versions are affected?
- Langflow <= 1.9.1; langflow (PyPI) ECOSYSTEM:introduced=0,fixed=1.9.2.
- Is there a fix for CVE-2026-48519?
- Yes. langflow (PyPI): upgrade to 1.9.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-48519 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-48519?
- Check whether you run Langflow or 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.9.2 or later
pip install "langflow>=1.9.2"
Technical details
A remote code execution (RCE) vulnerability exists in Langflow's 'Shareable Playground' (Public Flows) feature due to improper input validation of workflow payloads. The application exposes the `/api/v1/build_public_tmp` endpoint, which is designed to execute public flows for unauthenticated users. An attacker can provide a crafted JSON payload containing arbitrary Python code within the `data.nodes[X].data.node.template.code.value` field. When the server processes this request to build the graph and instantiate components, it executes the supplied Python code. This vulnerability is tracked as CVE-2026-48519 and is resolved in version 1.9.2.
Affected products
- langflow-ai Langflow < 1.9.2
Identifiers
- CVE-2026-48519
- GHSA-v5ff-9q35-q26f
- PYSEC-2026-243
Timeline
- 2026-05-27: advisory: Initial GitHub security advisory published
- 2026-06-23: disclosed: NVD publication date