CVE-2026-65013: Authorization Bypass Through User-Controlled Key in onlook repo
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.
AI Analysis
Technical Summary
CVE-2026-65013 is a broken object level authorization vulnerability in onlook repo versions <=0.2.32. Authenticated attackers can supply arbitrary UUIDs to tRPC API procedures such as project.get, member.remove, and chat.conversation.delete, bypassing authorization checks. This enables unauthorized reading, modification, and deletion of other users' projects, members, and conversation data. The issue was resolved in commit 423e2e9, but no formal patch or advisory details are available. The CVSS 4.0 score is 8.7, reflecting high severity with network attack vector, low attack complexity, no user interaction, and high impact on confidentiality, integrity, and availability.
Potential Impact
Authenticated attackers can bypass authorization controls to access and manipulate other users' resources including project data, membership, and conversation history. This compromises confidentiality, integrity, and availability of user data within the affected onlook repo versions.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The vulnerability was fixed in commit 423e2e9, so upgrading to a version including this commit or later is recommended once an official release is available. Until then, restrict access to trusted users and monitor for suspicious activity related to project, member, and conversation management APIs.
CVE-2026-65013: Authorization Bypass Through User-Controlled Key in onlook repo
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.
CVSS v4.0
Score 8.7high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-65013 is a broken object level authorization vulnerability in onlook repo versions <=0.2.32. Authenticated attackers can supply arbitrary UUIDs to tRPC API procedures such as project.get, member.remove, and chat.conversation.delete, bypassing authorization checks. This enables unauthorized reading, modification, and deletion of other users' projects, members, and conversation data. The issue was resolved in commit 423e2e9, but no formal patch or advisory details are available. The CVSS 4.0 score is 8.7, reflecting high severity with network attack vector, low attack complexity, no user interaction, and high impact on confidentiality, integrity, and availability.
Potential Impact
Authenticated attackers can bypass authorization controls to access and manipulate other users' resources including project data, membership, and conversation history. This compromises confidentiality, integrity, and availability of user data within the affected onlook repo versions.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The vulnerability was fixed in commit 423e2e9, so upgrading to a version including this commit or later is recommended once an official release is available. Until then, restrict access to trusted users and monitor for suspicious activity related to project, member, and conversation management APIs.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-07-21T11:32:54.897Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a60f1d29c2644c7f85877a9
Added to database: 07/22/2026, 16:37:38 UTC
Last enriched: 07/30/2026, 02:09:13 UTC
Last updated: 09/04/2026, 10:52:10 UTC
Views: 76
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.