Cross-user data access via missing ownership checks
Published Jun 23, 2026 · Updated Jun 23, 2026
Authorization bypass in Langflow OSS before 1.9.0 allows remote authenticated users to read, alter, or delete other users' data. Seven /api/v1/monitor endpoints accept resource IDs or flow_id values and query or mutate records without filtering them by the requester's user ID. Exploitation requires a valid account, knowledge or discovery of another user's identifier, and a multi-user deployment; exposed data includes messages, sessions, build artifacts, and LLM logs.
Summary
What happened
Authorization bypass in Langflow OSS before 1.9.0 allows remote authenticated users to read, alter, or delete other users' data. Seven /api/v1/monitor endpoints accept resource IDs or flow_id values and query or mutate records without filtering them by the requester's user ID. Exploitation requires a valid account, knowledge or discovery of another user's identifier, and a multi-user deployment; exposed data includes messages, sessions, build artifacts, and LLM logs.
The record
- CVE
- CVE-2026-33760
- Published
- Jun 23, 2026
- Updated
- Jun 23, 2026
- Vendor
- OpenBMC Project
- Product
- Langflow OSS
- Classifications
- CWE-639, T1565.001, T1213
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 23, 2026CVE publishedPublication date reported by the CVE source.
- Jun 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.9.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA-9c59-2mvc-vfr8 curl proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo