CVE-2026-65013

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-22. a secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: ghsa, secondary
Trending — 4 sources updated this weekElevated
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 v3
8.8
EG Score
8.8(high)
EG Risk
44(Track)
EG Risk 44/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
22.1%
KEV
Not listed

Published

July 22, 2026

Last Modified

July 24, 2026

Advisory Details (4)

Auto-updated Jul 22, 2026
Upstream fix merged — awaiting tagged release. Sources: github_pr, github_commit.
generic

Onlook tRPC Insecure Direct Object Reference via multiple procedures | Advisories | VulnCheck

https://www.vulncheck.com/advisories/onlook-trpc-insecure-direct-object-reference-via-multiple-procedures
github_commit

commit 423e2e924366 (onlook-dev/onlook)

Fix landed in onlook-dev/onlook commit 423e2e924366 — awaiting tagged release

https://github.com/onlook-dev/onlook/commit/423e2e924366419e418ee049093872d535eea41a
github_pr

fix(security): enforce project-membership authorization across all tRPC routers (IDOR)

Fix merged in onlook-dev/onlook PR #3129 on 2026-07-22 — awaiting tagged release

https://github.com/onlook-dev/onlook/pull/3129
generic

Cross-user IDOR across multiple tRPC procedures · Issue #3122 · onlook-dev/onlook · GitHub

https://github.com/onlook-dev/onlook/issues/3122

Vendor Advisories for CVE-2026-65013(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 9× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-24 14:18 UTCEPSS rescore
  2. 2026-07-24 14:18 UTCEPSS rescore
  3. 2026-07-23 14:18 UTCEPSS rescore
  4. 2026-07-23 14:18 UTCEPSS rescore
  5. 2026-07-23 03:22 UTCEG score recompute
  6. 2026-07-22 18:55 UTCEG score recompute
  7. 2026-07-22 18:55 UTCGHSA enrichment
  8. 2026-07-22 16:31 UTCEG score recompute
  9. 2026-07-22 16:30 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-65013?
CVE-2026-65013 is a high vulnerability published on July 22, 2026. 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…
When was CVE-2026-65013 disclosed?
CVE-2026-65013 was first published in the National Vulnerability Database on July 22, 2026, with the most recent update on July 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-65013 actively exploited?
CVE-2026-65013 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 22.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-65013?
CVE-2026-65013 has a CVSS v4.0 base score of 8.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-65013?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-65013, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-65013

Explore →

Is Your Infrastructure Affected by CVE-2026-65013?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs