Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.9amended

OneUptime ClickHouse SQL Injection via Aggregate Query Parameters

CVE-2026-32306GHSA-p5g2-jm85-8g35

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (oneuptime 10.0.23), 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.23
    Fixed in
    10.0.23

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
9.9 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS
  • CVE-2026-32306: 0.67% estimated exploitation activity in the next 30 days; percentile 52.19 (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.

Summary 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. Details Entry Point — Common/Server/API/BaseAnalyticsAPI.ts:88-98, 292-296: The POST /{modelName}/aggregate route deserializes aggregateBy directly from the request body: No schema validation is applied to aggregateBy. The object flows directly to the database service. No Validation — Common/Server/Services/AnalyticsDatabaseService.ts:276-278: The aggregationType field is only checked for existence, never validated against an…

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

    Amended from ghsa record GHSA-p5g2-jm85-8g35

  2. Revision 2 · amended ·

    Amended from osv record GHSA-p5g2-jm85-8g35

  3. Revision 1 · created ·

    Published from ghsa record GHSA-p5g2-jm85-8g35

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-32306

Advisory: OneUptime ClickHouse SQL Injection via Aggregate Query Parameters
IDs: CVE-2026-32306, GHSA-p5g2-jm85-8g35
Record: https://patchnext.com/advisories/cve-2026-32306 (revision 3, 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: Critical (CVSS 9.9)
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.23. A vendor fix does not mean a deployment is fixed.

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

## 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://github.com/advisories/GHSA-p5g2-jm85-8g35 (GitHub-reviewed advisory GHSA-p5g2-jm85-8g35 lists affected ranges: npm oneuptime >=0 <10.0.23)
- Verified: https://osv.dev/vulnerability/GHSA-p5g2-jm85-8g35 (OSV record GHSA-p5g2-jm85-8g35 lists affected ranges: npm oneuptime >=0 <10.0.23 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…