Cross-user API-key deletion via unchecked ownership
Published Mar 20, 2026 · Updated Mar 20, 2026
Authorization bypass in Langflow OSS before 1.9.0 allows remote authenticated users to delete other users' API keys by ID. The delete_api_key_route endpoint passes the path-supplied api_key_id to delete_api_key, which deletes the selected record without comparing its user_id with the current user's ID. A valid account and another key's UUID are required; deletion interrupts that user's API-dependent integrations.
Summary
What happened
Authorization bypass in Langflow OSS before 1.9.0 allows remote authenticated users to delete other users' API keys by ID. The delete_api_key_route endpoint passes the path-supplied api_key_id to delete_api_key, which deletes the selected record without comparing its user_id with the current user's ID. A valid account and another key's UUID are required; deletion interrupts that user's API-dependent integrations.
The record
- CVE
- CVE-2026-33053
- Published
- Mar 20, 2026
- Updated
- Mar 20, 2026
- Vendor
- OpenBMC Project
- Product
- Langflow OSS
- Classifications
- CWE-639, T1531
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 20, 2026CVE publishedPublication date reported by the CVE source.
- Mar 20, 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?
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
No public exploit references are available in this record.
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