CVE-2026-65013 Onlook tRPC Insecure Direct Object Reference via multiple procedures

High 8.7 Published Updated

Authenticated attackers can access and modify other users' project data, members, and conversations by supplying arbitrary UUIDs to tRPC API procedures.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is CVE-2026-65013?

CVE-2026-65013 is a high-severity missing authorization vulnerability in onlook repo, published on 22 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

Official 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.

Weakness: CWE-639

Which versions are affected by CVE-2026-65013?

How do I fix CVE-2026-65013?

No fix has been published for CVE-2026-65013 yet. Limit exposure of the affected software until one is available.

Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.

Is CVE-2026-65013 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-65013 exists.

Public exploit code: 1 proofs of concept on GitHub.

Sources

Also known as GHSA-j6x3-f5cf-2pg4.

Is CVE-2026-65013 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free