CVE-2026-77768

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: ghsa, secondary
Trending — 3 sources updated this weekElevated
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 6.5Exploit: Elevated riskExposed: 0

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

The report.get procedure in packages/trpc/src/routers/report.ts accepted only a reportId and returned getReportById(reportId) directly. The enforceAccess middleware in packages/trpc/src/trpc.ts evaluates membership only when the input carries a projectId or organizationId key, so an input consisting of a reportId alone passed through unchecked, and getReportById in packages/db/src/services/reports.service.ts performs a findUnique on the report id with no project scoping. Any authenticated user could therefore read the full configuration of any saved report on the instance, including the owning projectId, event series, filters, breakdowns and formulas, by supplying its identifier. The adjacent update, delete and duplicate procedures resolve the report first and check getProjectAccess against the report's own projectId, so the omission was specific to this procedure.

CVSS v3
6.5
EG Score
6.5(high)
EG Risk
45(Track)
EG Risk 45/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
Severity65% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
—
EPSS %ILE
—
KEV
Not listed

Published

August 21, 2026

Last Modified

August 21, 2026

Advisory Details (5)

Auto-updated Aug 21, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
generic

OpenPanel report.get Returns Any Report by Identifier Without Checking Project Access | Advisories | VulnCheck

https://www.vulncheck.com/advisories/openpanel-report-get-returns-any-report-by-identifier-without-checking-project-access
github Patch Available🟡 PoC Available

Cross-organization report read via missing ownership check in report.get · Advisory · Openpanel-dev/openpanel · GitHub

https://github.com/Openpanel-dev/openpanel/security/advisories/GHSA-9x7c-f87x-2243
github_commit

commit 0a51b6805eed (Openpanel-dev/openpanel)

Fix landed in Openpanel-dev/openpanel commit 0a51b6805eed — awaiting tagged release

https://github.com/Openpanel-dev/openpanel/commit/0a51b6805eed0b3da8376175acd5fa3d26819cb6
generic

openpanel/packages/trpc/src/routers/report.ts at e8a0602cda5a4d4b463f11d298a1b078c446bf33 · Openpanel-dev/openpanel · GitHub

https://github.com/Openpanel-dev/openpanel/blob/e8a0602cda5a4d4b463f11d298a1b078c446bf33/packages/trpc/src/routers/report.ts
generic

GitHub - Openpanel-dev/openpanel: OpenPanel is an open-source web and product analytics platform, an open-source alternative to Mixpanel with optional self-hosting. · GitHub

https://github.com/Openpanel-dev/openpanel

Vendor Advisories for CVE-2026-77768(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 7× in last 7d / 7× 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-08-21 18:18 UTCEG score recompute
  2. 2026-08-21 18:18 UTCGHSA enrichment
  3. 2026-08-21 17:40 UTCEG score recompute
  4. 2026-08-21 17:40 UTCGHSA enrichment
  5. 2026-08-21 11:21 UTCEG score recompute
  6. 2026-08-21 11:16 UTCEG score recompute
  7. 2026-08-21 11:14 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(4)

What is CVE-2026-77768?
CVE-2026-77768 is a medium vulnerability published on August 21, 2026. The report.get procedure in packages/trpc/src/routers/report.ts accepted only a reportId and returned getReportById(reportId) directly. The enforceAccess middleware in packages/trpc/src/trpc.ts evaluates membership only when the input carries a projectId or organizationId key, so an input…
When was CVE-2026-77768 disclosed?
CVE-2026-77768 was first published in the National Vulnerability Database on August 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-77768?
CVE-2026-77768 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-77768?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-77768, 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-77768

Explore →

Is Your Infrastructure Affected by CVE-2026-77768?

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

Start Free Scan →Browse All CVEs