Cross-tenant data access and manipulation via unchecked identifiers
Published Jul 22, 2026 · Updated Jul 22, 2026
Broken object authorization in Onlook 0.2.32 and earlier allows remote authenticated users to read, modify, or delete other users' data. Numerous tRPC procedures trust client-supplied resource UUIDs without verifying that the caller belongs to the owning project, while the database connection bypasses row-level security. Any account can target another user's known project or conversation identifier, exposing project details and permitting membership or conversation changes.
Summary
What happened
Broken object authorization in Onlook 0.2.32 and earlier allows remote authenticated users to read, modify, or delete other users' data. Numerous tRPC procedures trust client-supplied resource UUIDs without verifying that the caller belongs to the owning project, while the database connection bypasses row-level security. Any account can target another user's known project or conversation identifier, exposing project details and permitting membership or conversation changes.
The record
- CVE
- CVE-2026-65013
- Published
- Jul 22, 2026
- Updated
- Jul 22, 2026
- Vendor
- Onlook
- Product
- Onlook
- Classifications
- CWE-639, T1485, T1213
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 22, 2026CVE publishedPublication date reported by the CVE source.
- Jul 22, 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=0 <=0.2.32
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
- Cross-user IDOR live reproductionfunctional · 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