# CVE-2026-33142: OneUptime: ClickHouse SQL Injection via unvalidated column identifiers in sort, select, and groupBy parameters

> Attackers can inject arbitrary SQL into ClickHouse queries via unvalidated column identifiers in analytics endpoints, potentially reading or modifying data.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **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:** 20 Mar 2026
- **Updated:** 25 Mar 2026
- **Also known as:** GHSA-gcg3-c5p2-cqgg

## What is CVE-2026-33142?

CVE-2026-33142 is a high-severity SQL injection vulnerability in oneuptime, published on 20 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 version 10.0.34, the fix for CVE-2026-32306 (ClickHouse SQL injection via aggregate query parameters) added column name validation to the _aggregateBy method but did not apply the same validation to three other query construction paths in StatementGenerator. The toSortStatement, toSelectStatement, and toGroupByStatement methods accept user-controlled object keys from API request bodies and interpolate them as ClickHouse Identifier parameters without verifying they correspond to actual model columns. ClickHouse Identifier parameters are substituted directly into queries without escaping, so an attacker who can reach any analytics list or aggregate endpoint can inject arbitrary SQL through crafted sort, select, or groupBy keys. This issue has been patched in version 10.0.34.

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

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

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.34 |
| `oneuptime` | npm | All versions | 10.0.34 |

Products: Hackerbay Oneuptime.

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

Upgrade oneuptime to 10.0.34 or later.

## Is CVE-2026-33142 being exploited?

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

## Other vulnerabilities in oneuptime

- [CVE-2026-33396](https://insights.sbomify.com/CVE-2026-33396/): Code injection in oneuptime (critical 10.0)
- [CVE-2026-32306](https://insights.sbomify.com/CVE-2026-32306/): OneUptime ClickHouse SQL Injection via Aggregate Query Parameters (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)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-33142 is a high-severity SQL injection vulnerability in oneuptime, published on 20 Mar 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-33142 in the wild and no public exploit code.

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

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

## Sources

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

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