# CVE-2026-116807: OpenPanel before 3.0.0 ClickHouse SQL Injection via event.events tRPC Query


- **Severity:** High 7.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-4c79-56xr-vg4w, GHSA-pc3q-gw7f-p2x2

## What is CVE-2026-116807?

CVE-2026-116807 is a high-severity vulnerability in Openpanel-dev openpanel, published on 26 Oct 2026. 

### Official description

OpenPanel before 3.0.0 contains an sql injection vulnerability that allows authenticated users to bypass tenant scoping by injecting unescaped profile filter names into a JOIN subquery. Attackers can supply a crafted filter name with a trailing comment to bypass the project_id WHERE clause and read events from all projects.

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

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


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

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

## Is CVE-2026-116807 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116807 is a high-severity vulnerability in Openpanel-dev openpanel, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116807 in the wild and no public exploit code.

Affected product: Openpanel-dev openpanel. 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-116807/ (Markdown: https://insights.sbomify.com/CVE-2026-116807/index.md)
```

## Sources

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

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