CVE-2026-55255: langflow · Insecure Direct Object Reference
Affects langflowSource CVE Database V5
Exploited in the wild · KEV due 10 Jul 2026 : upgrade to 1.9.1 now.
Data as of 6 Nov 2026, 23:24 UTC
- KEV deadline
- US federal agencies must patch by this date; a sensible deadline for everyone else. Other KEV due dates
- EPSS
- 0.8% chance of exploitation in 30 days – higher than 59% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.9.1, 1.9.2
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:LExploitation evidence
t = 0 is the CVE’s publication on cve.org
Disclosed: evidence found.
CVE published 23 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
Public exploit code: GitHub proofs of concept
Exploited in the wildExploited: evidence found.
Listed in CISA KEV 14 days after disclosure
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
Timeline
CVE ID reserved
by GitHub, Inc.
, 7 days before disclosure
CVE published
on cve.org
, t = 0
In Threat Radar
record ingested
, 12 minutes after disclosure
Added to CISA KEV (opens in a new tab)
exploitation confirmed
, 14 days after disclosure
KEV remediation due
US federal deadline
, 17 days after disclosure
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, CISA KEV (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.
What to do
Upgrade langflow to 1.9.1; langflow-ai/langflow to 1.9.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| langflow-ailangflow | Affected
| Fixed in
|
GitHublangflow-ai/langflowpkg:github/langflow-ai/langflowOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
Langflow is a tool for building and deploying AI-powered agents and workflows. Prior to 1.9.1, an Insecure Direct Object Reference (IDOR) vulnerability in /api/v1/responses endpoint allows an authenticated attacker to execute any flow belonging to another user by specifying the victim's flow ID in the request. This vulnerability is fixed in 1.9.1.
References
- github.com/langflow-ai/langflow/security/advisories/GHSA-qrpv-q767-xqq2 (opens in a new tab)
- github.com/langflow-ai/langflow/pull/12832 (opens in a new tab)
- github.com/langflow-ai/langflow/commit/2c9f498d664a3c32698b57d7c5e752625291060e (opens in a new tab)
- webflow.sysdig.com/blog/understanding-langflow-cve-2026-55255-and-why-higher-cvss-vulnerabilities-arent-always-the-most-exploited (opens in a new tab)
- cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-55255 (opens in a new tab)