# CVE-2026-85615: Openpanel before 2.3.0 Cross-Tenant IDOR via report.getLayouts

> Authenticated attackers can read or delete other tenants' dashboard layouts by manipulating dashboard IDs in Openpanel.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/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:** 4 Sep 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-5cpv-vqvr-7mrh, GHSA-w9vr-cg67-9jp7

## What is CVE-2026-85615?

CVE-2026-85615 is a medium-severity missing authorization vulnerability in Openpanel-dev openpanel, published on 4 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Openpanel before 2.3.0 contains an insecure direct object reference vulnerability in the report.getLayouts and report.resetLayout tRPC procedures that fail to bind dashboardId to the authorized projectId. Authenticated attackers can supply an arbitrary victim dashboardId with their own projectId to read report layouts and configurations or delete dashboard grid arrangements across tenants.

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

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


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

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

## Is CVE-2026-85615 being exploited?

There is no known exploitation of CVE-2026-85615 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-85615 is a medium-severity missing authorization vulnerability in Openpanel-dev openpanel, published on 4 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-85615 in the wild and no public exploit code.

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-85615/ (Markdown: https://insights.sbomify.com/CVE-2026-85615/index.md)
```

## Sources

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

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