Quick answers
- Is CVE-2026-55881 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-55881 being exploited in the wild.
- How severe is CVE-2026-55881?
- Informational severity, with a CVSS score of 7.1, published 10 July 2026.
- Which products and versions are affected?
- OpenReplay >= 1.22.0, < 1.27.0.
- Is there a fix for CVE-2026-55881?
- A patch was published on 2026-05-05: Version 1.27.0 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-55881 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-55881?
- 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 Insecure Direct Object Reference (IDOR) vulnerability exists in the getFirstMob endpoint of OpenReplay. The root cause is a missing ownership validation: while the system verifies that a requested project ID belongs to the user's tenant, it fails to verify that the requested session ID actually belongs to that project. By providing a valid session ID from a different tenant in the path parameter, an authenticated attacker can obtain presigned S3 URLs for the first 15 seconds of DOM-replay data (dom.mobs and dom.mobe). This affects multi-tenant deployments where users are isolated by project. The vulnerability is resolved in version 1.27.0 by adding an explicit sessions.IsExists(projID, sessID) check in the backend handler.
Affected products
- OpenReplay OpenReplay >= 1.22.0, < 1.27.0
Timeline
- 2026-05-05: patched: Version 1.27.0 released
- 2026-06-11: other: Fix commit merged into main branch
- 2026-06-16: advisory: GitHub Security Advisory published
- 2026-07-10: disclosed: CVE published to NVD