Quick answers
- Is CVE-2026-45296 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-45296 being exploited in the wild.
- How severe is CVE-2026-45296?
- High severity, with a CVSS score of 7.7, published 28 May 2026.
- Which products and versions are affected?
- OpenReplay < 1.26.0.
- Is there a fix for CVE-2026-45296?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-45296 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-45296?
- Check whether you run OpenReplay 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
An improper access control vulnerability exists in OpenReplay's Python API due to a missing tenant-binding check in the 'app_apikey' routes. While the APIKeyAuth component validates that an API key is valid, the ProjectAuthorizer resolves 'projectKey' identifiers globally without ensuring the project belongs to the authenticated user's tenant. Because projectKeys are exposed in client-side browser code by design, an attacker with low-privileged credentials (any valid API key) can supply a victim's projectKey to enumerate user sessions and retrieve sensitive session event data. This bypasses tenant isolation in multi-tenant deployments. The issue is fixed in version 1.26.0.
Affected products
- OpenReplay OpenReplay < 1.26.0
Timeline
- 2026-05-08: advisory: GitHub Security Advisory published
- 2026-05-28: disclosed: NVD publication date