p PatchFirst

PatchFirst · Latest vulnerabilities

oneuptime vulnerabilities

Vulnerabilities published for oneuptime in the last 30 days: 0. Listed in the KEV catalogue: 0.

Filter vulnerabilities
Clear filters

Vulnerabilities: 5

  1. CVE-2026-33142

    High · CVSS 8.1EPSS 0.31%Fix available

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

    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 quer

    • Update to 10.0.34
    Published Updated
  2. CVE-2026-33143

    High · CVSS 8.7EPSS 0.18%Fix available

    OneUptime: WhatsApp Webhook Missing Signature Verification

    OneUptime is a solution for monitoring and managing online services. Prior to version 10.0.34, the WhatsApp POST webhook handler (/notification/whatsapp/webhook) processes incoming status update events without verifying the Meta/WhatsApp X-Hub-Signature-256 HMAC signature, allowing any unauthenticated attacker to send forged webhook payloads that manipulate notification delivery status records, suppress alerts, and corrupt audit trails. The codebase already implements proper signature verification for Slack webhooks. This issue has been patched in version 10.0.34.

    • Update to 10.0.34
    Published Updated
  3. CVE-2026-32598

    Medium · CVSS 6.9EPSS 0.24%Fix available

    OneUptime: Password Reset Token Logged at INFO Level

    OneUptime is a solution for monitoring and managing online services. Prior to 10.0.24, the password reset flow logs the complete password reset URL — containing the plaintext reset token — at INFO log level, which is enabled by default in production. Anyone with access to application logs (log aggregation, Docker logs, Kubernetes pod logs) can intercept reset tokens and perform account takeover on any user. This vulnerability is fixed in 10.0.24.

    • Update to 10.0.23
    Published Updated
  4. CVE-2026-32308

    High · CVSS 7.6EPSS 0.23%Fix available

    OneUptime: Stored XSS via Mermaid Diagram Rendering (securityLevel: "loose")

    OneUptime is a solution for monitoring and managing online services. Prior to 10.0.23, the Markdown viewer component renders Mermaid diagrams with securityLevel: "loose" and injects the SVG output via innerHTML. This configuration explicitly allows interactive event bindings in Mermaid diagrams, enabling XSS through Mermaid's click directive which can execute arbitrary JavaScript. Any field that renders markdown (incident descriptions, status page announcements, monitor notes) is vulnerable. This vulnerability is fixed in 10.0.23.

    • Update to 10.0.23
    Published Updated
  5. CVE-2026-32306

    Critical · CVSS 10EPSS 0.67%Fix available

    OneUptime ClickHouse SQL Injection via Aggregate Query Parameters

    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 v

    • Update to 10.0.23
    Published Updated

Check your server

Check your installed stack and versions against the current vulnerability feeds.

Check your server →