Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.1amended

OneUptime ClickHouse vulnerable to SQL Injection via unvalidated column identifiers in sort, select, and groupBy parameters

CVE-2026-33142GHSA-gcg3-c5p2-cqgg

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (oneuptime 10.0.34), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm oneuptime

    Affected
    < 10.0.34
    Fixed in
    10.0.34

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.1 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
EPSS
  • CVE-2026-33142: 0.31% estimated exploitation activity in the next 30 days; percentile 23.45 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

The fix for GHSA-p5g2-jm85-8g35 (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. Details Root cause StatementGenerator.ts has four methods that iterate over user-provided object keys to build SQL: | Method | Validates keys? | |--------|----------------| | toWhereStatement (line 292) | Yes - calls this.model.getTableColumn(key) | | toSortStatement (line…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-gcg3-c5p2-cqgg

  2. Revision 1 · created ·

    Published from osv record GHSA-gcg3-c5p2-cqgg

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-33142

Advisory: OneUptime ClickHouse vulnerable to SQL Injection via unvalidated column identifiers in sort, select, and groupBy parameters
IDs: CVE-2026-33142, GHSA-gcg3-c5p2-cqgg
Record: https://patchnext.com/advisories/cve-2026-33142 (revision 2, source checked 26 Oct 2026, 12:46 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: oneuptime 10.0.34. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm oneuptime: affected < 10.0.34; fixed in 10.0.34

## Suggested inspection (read-only)
- `npm ls oneuptime --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on oneuptime.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-gcg3-c5p2-cqgg (OSV record GHSA-gcg3-c5p2-cqgg lists affected ranges: npm oneuptime >=0 <10.0.34 (fixed))
- Verified: https://github.com/advisories/GHSA-gcg3-c5p2-cqgg (GitHub-reviewed advisory GHSA-gcg3-c5p2-cqgg lists affected ranges: npm oneuptime >=0 <10.0.34)

Commands are suggestions: review each one before running it.

Loading voting…