CVE-2026-65013
Auth users can access/modify others' projects and chats by supplying arbitrary UUIDs to tRPC APIs.
Is CVE-2026-65013 being exploited?
Not confirmed. CVE-2026-65013 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.52% probability of exploitation in the next 30 days.
How severe is CVE-2026-65013?
CVE-2026-65013 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-65013?
Yes. A fix has been recorded for CVE-2026-65013. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-65013 affect?
CVE-2026-65013 affects Onlook <= 0.2.32, tRPC APIs: project.get, tRPC APIs: member.remove, tRPC APIs: chat.conversation.delete. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-65013?
Upgrade Onlook to the commit/release including fix 423e2e9 and validate object-level auth.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated attackers can read, modify, and delete other users' projects, members, and conversation history via tRPC UUID parameters.
Immediate action required
- affected<= 0.2.32
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.