Live › vulnerability › CVE-2026-104316
Langflow OSS versions 1.0.0 through 1.12.3 lack a permission check on the endpoint that cancels background workflow jobs. An attacker with a valid account can stop another user's running flow with one HTTP request, losing that work in progress.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-29 16:25 UTC. All times on this page are UTC.
Teams running self-hosted Langflow OSS from 1.0.0 through 1.12.3 where more than one user has an account. Exposure requires an authenticated account, and the impact is cancelled background jobs rather than code execution or data theft. Single-user or non-Langflow deployments can skip it.
No product ranges from the sources yet.
pip show langflow or the image tag in your deployment.1.12.3; the source does not name the exact fixed release.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
IBM Langflow OSS 1.0.0 through 1.12.3 could allow an authenticated attacker to cancel any victim's running background workflow job by sending a single HTTP request, resulting in loss of in-progress compute work with no flow-level permission check.
This page as .md · .json · in your agent: get_signal("CVE-2026-104316")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.