---
id: "CVE-2026-18894"
kind: "vulnerability"
aliases: ["CVE-2026-18894"]
title: "Langflow: public workflows can run stored Python components under owner's context"
severity: "medium"
cvss: 6.5
epss: null
exploited: false
status: "open"
category: "ai-tooling"
products: []
ecosystems: []
tags: ["ai-tooling", "langflow", "python", "self-hosted"]
not_affected_if: ["no-public-flows", "version-outside-range"]
published_at: "2026-10-29T16:18:08+00:00"
first_seen_at: "2026-10-29T16:25:59+00:00"
updated_at: "2026-10-29T16:31:21+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-18894", "first_seen_at": "2026-10-29T16:25:59+00:00"}]
---

# Langflow: public workflows can run stored Python components under owner's context

IBM Langflow OSS 1.0.0 through 1.12.4 lets a remote attacker trigger Python component code already stored in a public workflow. That code runs inside the server process under the flow owner's runtime context, bypassing the intended trust boundary for public execution.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed Langflow version, for example with `pip show langflow`, and see whether it falls in 1.0.0 through 1.12.4.
- Look for flows marked public that contain custom Python components.

## Fix

- Langflow OSS: move to a version newer than `1.12.4`; the sources do not name the exact fixed version.

## Timeline

- 2026-10-29T16:25:59+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-18894

## From the sources

IBM Langflow OSS 1.0.0 through 1.12.4 could allow a remote attacker to trigger pre-existing stored Python component code in a public workflow, executing it under the flow owner's runtime context within the server process. This bypasses the intended trust boundary where public execution paths are restricted to server-trusted component code.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_