# CVE-2026-55881: OpenReplay: Cross-tenant session replay disclosure via missing session ownership check in first-mob endpoint

> Authenticated users can access other tenants' session replay recordings due to missing ownership checks, exposing sensitive user data.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jul 2026
- **Updated:** 13 Jul 2026
- **Also known as:** GHSA-w2x5-m7w5-479h

## What is CVE-2026-55881?

CVE-2026-55881 is a high-severity missing authorization vulnerability in openreplay, published on 10 Jul 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. 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.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-55881?


## How do I fix CVE-2026-55881?

No fix has been published for CVE-2026-55881 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-55881 being exploited?

There is no known exploitation of CVE-2026-55881 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-55881 and fix it if it is affected.

What it is: CVE-2026-55881 is a high-severity missing authorization vulnerability in openreplay, published on 10 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-55881 in the wild and no public exploit code.

Affected product: openreplay. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-55881/ (Markdown: https://insights.sbomify.com/CVE-2026-55881/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-55881
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-55881
- OSV: https://osv.dev/vulnerability/CVE-2026-55881

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-55881/
Summaries are generated and may contain mistakes; the official description above is the record.