langflow-ai · Langflow · published 2026-10-05

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

This month Public proof-of-concept exists (SSVC exploitation: poc).

CVE-2026-105698 has a public proof-of-concept exploit, but no confirmed exploitation in the wild. EPSS estimates a 0.2% chance of exploitation in the next 30 days, higher than 13% of all CVEs. This Langflow vulnerability: CVSS 5.4 (v3.1). Fixed upstream in Langflow 1.12.0, 1.10.3, 1.10.1, 0.10.3 (+2 more). Patch in your normal monthly cycle.

Share this

Remediation#

Fixed upstream in Langflow 1.12.0, 1.10.3, 1.10.1, 0.10.3, 0.10.1, 0.1.2.

Patch events

  1. This monthSecurity release

    AI toolingLangflow

    Langflow security fixes: 2 CVEs

    Upgrade to 1.12.01.10.31.10.10.10.30.10.10.1.2

    Why: CVE-2026-105697: EPSS 1.5% with high severity (CVSS 9.9).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.2% (14th pct)FIRST EPSS v2026.06.15
CVSS base score5.4 (v3.1)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
CNA / CISA ADP
SSVC exploitationpocCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impactpartialCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

Langflow is a tool for building and deploying AI-powered agents and workflows. From 1.0.0 until 1.10.1, Langflow did not verify flow ownership in the deprecated POST /api/v1/build/{flow_id}/vertices and POST /api/v1/build/{flow_id}/vertices/{vertex_id} handlers. Through version 1.7.1, an unauthenticated caller who knew another user's flow UUID could reach these handlers; from version 1.7.2 through 1.10.0, callers had to authenticate but needed no elevated privileges. Such a caller could cause retrieve_vertices_order to load and cache the private graph, enumerate its vertex identifiers, and use build_vertex to execute selected vertices and receive their results. build_graph_from_db_no_cache performed a primary-key lookup without an owner filter. This could disclose private flow structure, configured values, and selected outputs and could trigger victim-configured side effects and build-history records, although it did not expose the victim's variable-store credentials or permit modification of the stored flow. This issue is fixed in Langflow 1.10.1 and langflow-base 0.10.1.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →