# CVE-2026-32306: OneUptime ClickHouse SQL Injection via Aggregate Query Parameters

> Authenticated users can inject SQL into ClickHouse queries via telemetry API parameters, allowing data theft, modification, and potential code execution.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Mar 2026
- **Updated:** 14 Mar 2026
- **Also known as:** GHSA-p5g2-jm85-8g35

## What is CVE-2026-32306?

CVE-2026-32306 is a critical SQL injection vulnerability in oneuptime, published on 12 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

OneUptime is a solution for monitoring and managing online services. Prior to 10.0.23, the telemetry aggregation API accepts user-controlled aggregationType, aggregateColumnName, and aggregationTimestampColumnName parameters and interpolates them directly into ClickHouse SQL queries via the .append() method (documented as "trusted SQL"). There is no allowlist, no parameterized query binding, and no input validation. An authenticated user can inject arbitrary SQL into ClickHouse, enabling full database read (including telemetry data from all tenants), data modification, and potential remote code execution via ClickHouse table functions. This vulnerability is fixed in 10.0.23.

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

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

2 open source packages ship an affected version, including oneuptime. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `oneuptime` | npm | All versions | 10.0.23 |
| `oneuptime` | npm | All versions | 10.0.23 |

Products: Hackerbay Oneuptime.

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

Upgrade oneuptime to 10.0.23 or later.

## Is CVE-2026-32306 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32306 exists.

## Other vulnerabilities in oneuptime

- [CVE-2026-33396](https://insights.sbomify.com/CVE-2026-33396/): Code injection in oneuptime (critical 10.0)
- [CVE-2026-30956](https://insights.sbomify.com/CVE-2026-30956/): OneUptime has authorization bypass via client‑controlled is-multi-tenant-query header (critical 10.0)
- [CVE-2026-30957](https://insights.sbomify.com/CVE-2026-30957/): OneUptime Synthetic Monitor RCE via exposed Playwright browser object (critical 10.0)
- [CVE-2026-30887](https://insights.sbomify.com/CVE-2026-30887/): OneUptime Affected by Unsandboxed Code Execution in Probe Allows Any Project Member to Achieve RCE (critical 10.0)
- [CVE-2026-30921](https://insights.sbomify.com/CVE-2026-30921/): OneUptime Synthetic Monitor RCE via exposed Playwright browser object (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-32306 is a critical SQL injection vulnerability in oneuptime, published on 12 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32306 exists.

Affected packages and fixed versions:
- oneuptime (npm): affected all versions; fixed in 10.0.23
- oneuptime (npm): affected all versions; fixed in 10.0.23

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-32306/ (Markdown: https://insights.sbomify.com/CVE-2026-32306/index.md)
```

## Sources

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

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