# CVE-2026-45296: OpenReplay: Cross-tenant information disclosure in app_apikey projectKey routes via missing tenant binding

> Attackers with valid API keys can access other tenants' session data by exploiting missing tenant binding in project key validation.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A: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:** 28 May 2026
- **Updated:** 30 May 2026
- **Also known as:** GHSA-8wmc-vpmf-cjf5

## What is CVE-2026-45296?

CVE-2026-45296 is a high-severity missing authorization vulnerability in openreplay, published on 28 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

OpenReplay is a self-hosted session replay suite. Prior to 1.26.0, OpenReplay's Python API exposes several app_apikey routes that trust a caller-provided projectKey after validating only that the API key itself is valid and that the target projectKey exists. The authorization flow does not verify that the authenticated API key and the requested project belong to the same tenant. Because the public tracker design exposes projectKey to browser-side code, an attacker who owns any valid API key for their own tenant can target another tenant's project by reusing that public projectKey. The vulnerable routes allow the attacker to enumerate victim user sessions and then retrieve sensitive session event data across the tenant boundary. This vulnerability is fixed in 1.26.0.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2026-45296 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-45296 is a high-severity missing authorization vulnerability in openreplay, published on 28 May 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-45296 in the wild and no public exploit code.

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

## Sources

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

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