dbcve.org
OneuptimeApplication · Hackerbay

CVE-2026-32306

CRITICAL · 9.9 CVSS v3.1 Published 2026-03-13
Fix available
A fix is available. Upgrade to 10.0.23 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

OneUptime telemetry aggregation API versions prior to 10.0.23 directly interpolate user-controlled parameters (aggregationType, aggregateColumnName, aggregationTimestampColumnName) into ClickHouse SQL queries via .append() without sanitization, parameterized binding, or allowlisting, enabling authenticated users to inject arbitrary SQL for full database access and potential RCE.

MitigationUpgrade to OneUptime version 10.0.23 or later which implements proper input validation and parameterized query handling for the telemetry aggregation API.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
OneuptimeApplication
Affected:< 10.0.23

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed OneUptime version
    Locate the version file, package.json, or docker image tag used in your deployment. Common locations: package.json in the application root, a VERSION file, or the docker container image tag.
    Affected if The installed version is below 10.0.23 (e.g., 10.0.0 through 10.0.22).
  2. Determine if telemetry aggregation API is accessible
    Check your application routing or API endpoint configuration for routes handling telemetry aggregation. Look for endpoints accepting aggregationType, aggregateColumnName, or aggregationTimestampColumnName parameters.
    Affected if The telemetry aggregation API endpoints are exposed and accessible to authenticated users.
  3. Verify ClickHouse is in use
    Check your application configuration files or environment variables for ClickHouse connection settings (e.g., CLICKHOUSE_HOST, CLICKHOUSE_URL, or similar database connection configurations).
    Affected if ClickHouse is configured as a data store for the telemetry system.
  4. Check API authentication configuration
    Review your authentication settings to confirm whether users can authenticate to the telemetry API endpoints.
    Affected if Authenticated users have access to the aggregation API endpoints.

You are affected if running OneUptime version below 10.0.23 with the telemetry aggregation API enabled and accessible to authenticated users, and ClickHouse is used as the underlying database.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.0.23 or later
Fixed in 10.0.23
Interim mitigation

Upgrade to OneUptime version 10.0.23 or later which implements proper input validation and parameterized query handling for the telemetry aggregation API.

Recommended fix High confidence

10.0.23

  1. Backup your current OneUptime installation and database before proceeding with the upgrade
  2. Upgrade OneUptime to version 10.0.23 (or the latest version that includes the fix)
  3. After upgrade, verify the telemetry aggregation API endpoint no longer accepts unsanitized SQL in aggregationType, aggregateColumnName, and aggregationTimestampColumnName parameters
  4. Confirm the .append() method is no longer used with user-controlled input in the telemetry aggregation API
Caveat Review OneUptime 10.0.23 release notes for any breaking changes specific to this release

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Oneuptime Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32306 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-32306 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data