Skip to content
HighVulnerability

GHSA-8c4j-f57c-35cf: Langflow: Authenticated Users Can Read, Modify, and Delete Any Flow via Missing Ownership Check

Published
Record updated
View JSON
Affected
  • langflow-base <= 0.5.0, fixed in 0.5.1, released August 28, 2025, 211 days before disclosure
  • langflow <= 1.5.0, fixed in 1.5.1, released August 28, 2025, 211 days before disclosure
Known exploitation
Not listed in the CISA Known Exploited Vulnerabilities catalog at the last check.
EPSS
0.5%

Summary

Langflow's `_read_flow` helper in `src/backend/base/langflow/api/v1/flows.py` omitted an ownership check when `AUTO_LOGIN` was `False`, so any authenticated user could read, modify, or delete another user's flow via `GET/PATCH/DELETE /api/v1/flow/{flow_id}`. Exposed data included embedded plaintext API keys, and attackers could alter other users' AI agent logic. The flaw was introduced by conditional logic meant to support public example flows (`user_id = NULL`) under auto-login mode.

Mitigation

Fixed in PR #8956, which removes the `AUTO_LOGIN` conditional and unconditionally scopes the query to the requesting user with `Flow.user_id == user_id`. A cross-user isolation test, `test_read_flows_user_isolation`, was added to prevent regression.