Quick answers
- Is CVE-2026-85615 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-85615 being exploited in the wild.
- How severe is CVE-2026-85615?
- Medium severity, with a CVSS score of 6.4, published 4 September 2026.
- Which products and versions are affected?
- OpenPanel before 2.3.0.
- Is there a fix for CVE-2026-85615?
- A patch was published on 2026-09-04: version 2.3.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-85615 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-85615?
- Check whether you run OpenPanel at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The report.getLayouts and report.resetLayout tRPC procedures contain an insecure direct object reference (IDOR) vulnerability rooted in missing authorization binding. Both handlers accept {dashboardId, projectId} input and validate only projectId via getProjectAccess(userId, projectId); they never verify that the supplied dashboardId actually belongs to that projectId. The underlying database queries filter solely by attacker-controlled dashboardId (where: { report: { dashboardId } }) without tenant scoping, allowing an authenticated user to supply their own valid projectId paired with any victim's dashboardId to read report layouts and full Report configuration rows or delete reportLayout rows. Dashboard IDs are low-entropy slugs (4-digit suffix only on collision), making victim dashboards easily enumerable. No user interaction is required. The fix is to bind dashboardId to projectId before query execution, as correctly implemented in the report.list handler. Patches are available in version 2.3.0.
Affected products
- Openpanel Openpanel before 2.3.0
Timeline
- 2026-08-20: disclosed
- 2026-09-04: patched: version 2.3.0