Quick answers
- Is CVE-2026-32306 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-32306 being exploited in the wild.
- How severe is CVE-2026-32306?
- Critical severity, with a CVSS score of 9.9, published 13 March 2026.
- Which products and versions are affected?
- OneUptime 10.0.22.
- Is there a fix for CVE-2026-32306?
- A patch was published on 2026-03-13: Version 10.0.23 contains the fix Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-32306 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-32306?
- Check whether you run Hackerbay Oneuptime or OneUptime at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a SQL injection in the analytics aggregation endpoints (/api/log/aggregate, /api/span/aggregate, /api/metric/aggregate). User-controlled parameters (aggregationType, aggregateColumnName, aggregationTimestampColumnName) are deserialized from the request body with no schema validation and concatenated directly into ClickHouse SQL queries via the .append() method, which performs raw string concatenation. The aggregationType field passes only a truthiness check (if (aggregateBy.aggregationType)) rather than validation against an allowlist of safe values (e.g., COUNT, SUM, AVG). An authenticated user of any role can craft a POST request containing SQL injection payloads in aggregationType to execute arbitrary queries, exfiltrate cross-tenant telemetry data, or abuse ClickHouse table functions for file reading. A patch is available in version 10.0.23.
Affected products
- OneUptime OneUptime 10.0.22
Identifiers
- CVE-2026-32306
- GHSA-p5g2-jm85-8g35
Timeline
- 2026-03-13: disclosed
- 2026-03-13: patched: Version 10.0.23 contains the fix