# CVE-2026-77769: OpenPanel report.list Queries Reports by an Unverified dashboardId, Crossing Organization Boundaries

> Authenticated users can read reports from other organizations by supplying a valid project ID with an unverified dashboard ID.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Aug 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-3q95-vc6f-vc9v, GHSA-mrm7-hxjw-vff5

## What is CVE-2026-77769?

CVE-2026-77769 is a high-severity missing authorization vulnerability in Openpanel-dev openpanel, published on 21 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The report.list procedure in packages/trpc/src/routers/report.ts accepted a projectId and a dashboardId and returned getReportsByDashboardId(dashboardId). The enforceAccess middleware in packages/trpc/src/trpc.ts verified membership for the supplied projectId, but nothing verified that the supplied dashboardId belonged to that project, and getReportsByDashboardId in packages/db/src/services/reports.service.ts selects reports by dashboardId alone with no project scoping. An authenticated user could therefore pair a projectId from their own organization, which satisfies the middleware, with a dashboardId belonging to another organization and receive every report in that dashboard. A correctly scoped helper, listReportsCore, already existed in the same service file and resolves the dashboard through getDashboardById(dashboardId, projectId) before returning reports, but the router did not use it.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-77769?


## How do I fix CVE-2026-77769?

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

## Is CVE-2026-77769 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-77769 and fix it if it is affected.

What it is: CVE-2026-77769 is a high-severity missing authorization vulnerability in Openpanel-dev openpanel, published on 21 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-77769 exists.

Affected product: Openpanel-dev openpanel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-77769/ (Markdown: https://insights.sbomify.com/CVE-2026-77769/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-77769
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-77769
- OSV: https://osv.dev/vulnerability/CVE-2026-77769

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-77769/
Summaries are generated and may contain mistakes; the official description above is the record.