Description

Onlook through 0.2.32, fixed in commit 423e2e9, contains a broken object level authorization vulnerability that allows authenticated attackers to access and manipulate other users' resources by supplying arbitrary UUID values to tRPC API procedures including project.get, member.remove, and chat.conversation.delete. Attackers can provide arbitrary projectId or conversationId values without authorization validation to read, modify, and delete other users' project data, members, and conversation history.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "8.8",
  "pubDate": "2026-07-22T17:16:59.143Z",
  "pubdate": "2026-07-22T17:16:59.143Z",
  "executiveSummary": "Onlook through version 0.2.32 contains a critical Broken Object Level Authorization (BOLA) vulnerability within its tRPC API procedures. This security flaw enables authenticated malicious actors to bypass access controls and interact with unauthorized resources belonging to other users. The primary impact includes the unauthorized reading, modification, and deletion of sensitive project data, member associations, and chat conversation histories. Affected systems comprise Onlook versions up to 0.2.32, which lack proper authorization checks on specific backend procedures. The risk implications are severe, as an attacker with standard authentication capabilities can manipulate critical objects across tenant or user boundaries simply by supplying arbitrary identifiers. Exploitation requires valid authentication to interact with the tRPC API endpoints, but no elevated privileges are necessary. Remediation is available via the vendor fix introduced in commit 423e2e9, which addresses the lack of authorization validation.",
  "technicalDetails": "The vulnerability stems from insufficient validation of object-level permissions within the tRPC API backend procedures of Onlook through version 0.2.32. Specifically, the application fails to verify whether the currently authenticated user possesses the necessary administrative or ownership rights over the requested resource identifiers before executing database queries or state changes. The vulnerable components include several specific tRPC API procedures, namely project.get, member.remove, and chat.conversation.delete. The root cause is the absence of programmatic checks confirming that supplied UUID values—such as projectId or conversationId—map to resources authorized for access by the calling session context. An attacker initiates the attack flow by authenticating to the Onlook application to obtain a valid session. Subsequently, the attacker crafts arbitrary tRPC API requests targeting the vulnerable procedures, substituting the legitimate resource identifiers with guessed, enumerated, or otherwise harvested UUID values belonging to other users or projects. For instance, by invoking the project.get procedure with an arbitrary projectId, the attacker can retrieve confidential project data without authorization. Similarly, calling member.remove or chat.conversation.delete with unauthorized UUIDs enables the deletion of project members and the complete removal of foreign conversation histories. The network exposure is dictated by the accessibility of the tRPC API interface. Authentication is required to reach the vulnerable procedures, but privilege requirements are limited to a standard authenticated user state, as the backend software improperly trusts the client-supplied parameters without performing contextual authorization enforcement. Post-exploitation impact includes complete data confidentiality breaches, unauthorized destruction of conversation threads, and unauthorized tampering with team member memberships."
}