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.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
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
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.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2026-45296 being exploited?
There is no known exploitation of CVE-2026-45296 in the wild and no public exploit code.
Sources
Also known as GHSA-8wmc-vpmf-cjf5.