# CVE-2026-45297: Cross-tenant IDOR on feature-flag and assist-stats routes via {project_id} case mismatch

> Authenticated users can access or modify other tenants' feature flags due to improper authorization checks on project identifiers.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/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:** 28 May 2026
- **Updated:** 29 May 2026
- **Also known as:** GHSA-5m23-rcj4-cgjx

## What is CVE-2026-45297?

CVE-2026-45297 is a medium-severity missing authorization vulnerability in openreplay, published on 28 May 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. Prior to 1.26.0, there is a cross-tenant IDOR on feature-flag and assist-stats routes via {project_id} case mismatch. ProjectAuthorizer.__call__ (OSS api/auth/auth_project.py:14-38 and EE ee/api/auth/auth_project.py:14-46) only runs projects.is_authorized(project_id, tenant_id, user_id) + projects.get_project(tenant_id, project_id) when self.project_identifier == "projectId" (camelCase). For EE multi-tenant, feature-flag queries only filter on project_id, never tenant_id. Any authenticated user in tenant A can read/update/delete feature-flag rows belonging to tenant B by iterating the sequential integer project_id + feature_flag_id. OSS is single-tenant by design ({"errors":["tenants already registered"]} on second signup) so there's no cross-tenant impact This vulnerability is fixed in 1.26.0.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-863 (Incorrect Authorization), CWE-285 (Improper Authorization)

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


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

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

## Is CVE-2026-45297 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-45297 is a medium-severity missing authorization vulnerability in openreplay, published on 28 May 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-45297 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-45297/ (Markdown: https://insights.sbomify.com/CVE-2026-45297/index.md)
```

## Sources

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

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