Advisory record · GHSA-gh98-4phw-6fmw

Langflow : Cross-user flow access and vertex execution via deprecated /api/v1/build/{flow_id}/vertices endpoints

CVSS 5.4 MediumEPSS 0.0022 · 13th percentile

Published by the GitHub Advisory Database at 7 Oct 2026, 20:36 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
langflowPyPI>=1.0.0, <1.10.11.10.1
langflow-basePyPI<0.10.10.10.1
Identifiers
GHSA-gh98-4phw-6fmw · CVE-2026-105698 · PYSEC-2026-4234 · PYSEC-2026-4238
Weakness (CWE)
CWE-639 · CWE-862
Published
7 Oct 2026
Updated
15 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Langflow versions from 1.0.0 before 1.10.1 (and langflow-base before 0.10.1) let any authenticated user reach two deprecated chat API endpoints that skip the flow ownership check. An attacker who knows another user's flow ID can read that flow's vertex IDs, component types and outputs of vertices they build, and trigger execution of those vertices. Upgrade to langflow 1.10.1 or langflow-base 0.10.1 or later. If upgrading is not immediately possible, block the POST paths matching /api/v1/build/*/vertices and /api/v1/build/*/vertices/* at a reverse proxy, since the Langflow UI does not use them.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
5.4 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0022, the 13th percentile, on 9 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:08 UTC First seen by agentprime
  2. 31 Oct 2026, 14:08 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.