CVE-2026-48519 is a critical-severity code injection vulnerability in langflow (pip), affecting versions <= 1.9.1. It is fixed in 1.9.2.
Summary The "Shareable Playground" (or "Public Flows" in code) contains a critical RCE vulnerability. Simply sharing a flow exposes the deployment to RCE risk by authenticated users. Tested on commit 2d67402b1dbaefcbce85a244d4a6cd5e4bda1cfe 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. 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. See PoC for an example. PoC Reproduction: Create a new flow and add a Chat Input node to it Share the flow ("Shareable Playground") Access the public link with the browser developers tools open and execute the flow. Find the /api/v1/buildpublictmp route and copy as cURL Edit the data.nodes[X].data.node.template.code.value JSON field with any python code and run the cURL command. Example PoC (replace flow ID with the correct one), and download testwithpython.json: Search for touch /tmp/pwned in the testwithpython.json and edit for any other code. The stacktrace for the code executed is: Impact Unauthenticated RCE on any deployment with a shareable playground. Ori Lahav Security Researcher @ Rubrik Inc.
Untrusted input is evaluated as executable code within the application's runtime environment. Typical impact: arbitrary code execution within the application's privilege context.
CVE-2026-48519 has a CVSS score of 9.6 (Critical). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.
A fixed version is available (1.9.2). Upgrading removes the vulnerable code path.
pip
langflow (<= 1.9.1)langflow → 1.9.2 (pip)Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.
Kodem's Application Detection and Response identifies whether CVE-2026-48519 is reachable in your applications. Explore runtime application protection for your team.
See if CVE-2026-48519 is reachable in your applications. Get a demo
Upgrade langflow to 1.9.2 or later to resolve this vulnerability.
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
CVE-2026-48519 is a critical-severity code injection vulnerability in langflow (pip), affecting versions <= 1.9.1. It is fixed in 1.9.2. Untrusted input is evaluated as executable code within the application's runtime environment.
CVE-2026-48519 has a CVSS score of 9.6 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
langflow (pip) versions <= 1.9.1 is affected.
Yes. CVE-2026-48519 is fixed in 1.9.2. Upgrade to this version or later.
Whether CVE-2026-48519 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
Upgrade langflow to 1.9.2 or later.