# CVE-2026-57230: OpenReplay: Authenticated ClickHouse SQL injection via session search

> Authenticated users can inject SQL into ClickHouse queries to read arbitrary data and disrupt session search functionality in multi-tenant OpenReplay deployments.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Jul 2026
- **Updated:** 13 Jul 2026
- **Also known as:** GHSA-vxf8-j7jx-p65x

## What is CVE-2026-57230?

CVE-2026-57230 is a medium-severity SQL injection vulnerability in openreplay, published on 10 Jul 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

OpenReplay is a self-hosted session replay suite. Prior to 1.27.0, the session search and analytics API in enterprise editions with multi-tenancy enabled built ClickHouse queries by inserting user input into the query string, including two positions that took input without escaping, allowing an authenticated member to read any ClickHouse table through blind boolean and time-based exfiltration and to break the project's session search for all viewers until the stored key is removed. This issue is fixed in version 1.27.0.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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


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

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

## Is CVE-2026-57230 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-57230 is a medium-severity SQL injection vulnerability in openreplay, published on 10 Jul 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-57230 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-57230/ (Markdown: https://insights.sbomify.com/CVE-2026-57230/index.md)
```

## Sources

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

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