OpenReplay is a self-hosted session replay suite. From 1.22.0 before 1.27.0, getFirstMob returned 15-second presigned S3 download URLs for a session's DOM-replay recording based solely on the session path parameter, while validateProjectAccess checked only that the project belonged to the requester's tenant and did not verify that the session belonged to that project, allowing any authenticated low-privilege user to read another tenant's first 15 seconds of session-replay recording data. This issue is fixed in version 1.27.0.
CVE-2026-55881
This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 84% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.1
- EG Score
- 7.1(medium)
- EPSS
- 15.7%
- KEV
- Not listed
Published
July 10, 2026
Last Modified
July 10, 2026
Advisory Details (4)
Auto-updated Jul 10, 2026Cross-tenant session replay disclosure via missing session ownership check in first-mob endpoint · Advisory · openreplay/openreplay · GitHub
https://github.com/openreplay/openreplay/security/advisories/GHSA-w2x5-m7w5-479hv1.27.0
Patch available: openreplay/openreplay v1.27.0
https://github.com/openreplay/openreplay/releases/tag/v1.27.0fix(backend): add session ownership check to first-mob handler
Fix merged in openreplay/openreplay PR #4692 on 2026-06-11 — awaiting tagged release
https://github.com/openreplay/openreplay/pull/4692commit ddd09117f644 (openreplay/openreplay)
Fix landed in openreplay/openreplay commit ddd09117f644 — awaiting tagged release
https://github.com/openreplay/openreplay/commit/ddd09117f644a309c7b040cda0a11ff9433e9e49Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 10× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 04:28 UTCEG score recompute
- 2026-07-12 17:23 UTCEG score recompute
- 2026-07-12 06:18 UTCEG score recompute
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 19:12 UTCEG score recompute
- 2026-07-11 08:08 UTCEG score recompute
- 2026-07-10 21:03 UTCEG score recompute
- 2026-07-10 21:02 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-639
- CVE-2018-25270EG 9.8CRITICAL
- CVE-2017-20223EG 9.8CRITICAL
- CVE-2019-25487EG 9.8EPSS 94%CRITICAL
- CVE-2019-25235EG 9.8CRITICAL
- CVE-2020-16088EG 9.8CRITICAL
- CVE-2019-15310EG 9.8EPSS 94%CRITICAL
- CVE-2020-11658EG 9.8CRITICAL
- CVE-2019-15913EG 9.8CRITICAL
- CVE-2019-16340EG 9.8EPSS 97%CRITICAL
- CVE-2019-13360EG 9.8EPSS 98%CRITICAL
Frequently asked(5)
What is CVE-2026-55881?
When was CVE-2026-55881 disclosed?
Is CVE-2026-55881 actively exploited?
What is the CVSS score of CVE-2026-55881?
How do I remediate CVE-2026-55881?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-55881
Is Your Infrastructure Affected by CVE-2026-55881?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.