Home

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.

PUBLISHED Reserved 2026-05-11 | Published 2026-05-28 | Updated 2026-05-30 | Assigner GitHub_M




HIGH: 7.7CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

Problem types

CWE-284: Improper Access Control

Product status

< 1.26.0
affected

References

github.com/...replay/security/advisories/GHSA-8wmc-vpmf-cjf5

cve.org (CVE-2026-45296)

nvd.nist.gov (CVE-2026-45296)

Download JSON