Skip to content
Server Security Center
KEVhigh8.4

CVE-2026-55255: Langflow Authorization Bypass Through User-Controlled Key

Langflow · listed in the CISA catalog of actively exploited vulnerabilities since 2026-07-07.

CVSS v3.1 (CVE record)
8.4
high
EPSS (exploit probability, 30 days)
0.9%
higher than 60.1% of all CVEs
Added to CISA KEV
2026-07-07
US federal due date 2026-07-10
Automatable (CISA SSVC)
no
technical impact: total

CVE-2026-55255 explained

CVE-2026-55255 is an Insecure Direct Object Reference (IDOR) flaw in the /api/v1/responses endpoint of Langflow, a tool for building and deploying AI-powered agents and workflows. An authenticated user can run flows that belong to other users. CISA lists it as known to be exploited, so affected servers need prompt attention.

Impact

An attacker with a valid low-privilege account can execute any other user's flow by supplying that flow's ID. No user interaction is needed. The impact on confidentiality and integrity is high, and the scope is changed, so effects can reach beyond Langflow itself. CISA rates the technical impact as total. CISA rates it as not automatable, and the attack complexity is high. Attackers are known to use this vulnerability.

Who is affected

The CVE record lists langflow-ai langflow versions < 1.9.1 as affected. The record's fixedIn field names no fixed version. However, the description states that the vulnerability is fixed in 1.9.1. Check the vendor advisory to confirm the correct release for your deployment.

Written with AI from the data on this page and checked against it automatically.

Official 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.

CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA’s “Forensics Triage Requirements”. Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • langflow-ai langflow
    Affected
    • < 1.9.1
    Fixed in
    not stated

How to fix it

  • The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
  • Vendor advisory: github.com/langflow-ai/langflow/pull/12832
  • CISA's deadline for US federal agencies: 2026-07-10 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Upgrade Langflow to 1.9.1 or later, as stated in the vulnerability description, after confirming it in the vendor advisory.
  2. Apply any mitigations in the vendor advisory and follow CISA's required action, including BOD 26-04 guidance.
  3. Restrict network access to Langflow servers and avoid exposing them directly to the internet.
  4. Review user accounts and remove unneeded or untrusted accounts that could authenticate to Langflow.
  5. Check logs for flow executions by users who do not own those flows, and look for other signs of compromise.

The CVE record's fixed-version field is empty, but the description states the issue is fixed in 1.9.1. Confirm this in the vendor advisory and upgrade. Until then, apply vendor mitigations and limit network exposure and user access. Per CISA's required action, discontinue use of the product if mitigations are unavailable.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-639 Authorization Bypass Through User-Controlled Key

Questions about CVE-2026-55255

Does an attacker need an account to exploit this?
Yes. The attacker must be authenticated, with low privileges. They can then execute flows belonging to other users by specifying the victim's flow ID.
Is this vulnerability being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2026-07-07, with a US federal due date of 2026-07-10. Whether it is used in ransomware campaigns is unknown.
Which version fixes it?
The description states the vulnerability is fixed in 1.9.1. All versions < 1.9.1 are affected. The record's fixedIn field is empty, so confirm the fixed release in the vendor advisory.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.