/

CVE-2026-34758

Severity:

CRITICAL RISK

(9.1)

Missing Authentication in OneUptime

CVE-2026-34758

Analyzed

Vulnerability type

Category:

Missing Authentication

CWE:

CWE-306

Impact:

Abuse of Notification Channels and Unauthorized Resource Consumption

Severity:

CRITICAL RISK

(9.1)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

OneUptime contained missing authentication on notification test and phone number management endpoints, allowing unauthenticated users to trigger SMS, calls, emails, and WhatsApp messages, and to purchase phone numbers.

When exposed, these endpoints can be abused for large-scale messaging, fraud, and unexpected resource consumption without any valid user account.

Affected context

The vulnerability occurs in OneUptime deployments where notification test and phone number management endpoints are network-accessible from untrusted environments (e.g., public internet) and were not protected by authentication or proper access control checks.

It is relevant in environments that integrate SMS, voice, email, or WhatsApp providers and support phone number provisioning through the platform.

The risk is elevated when those services are linked to billable third-party APIs or when rate limits and usage monitoring are weak or absent.

Exploit preconditions

  • Attack surface: HTTP(S) endpoints for notification testing and phone number management exposed by the OneUptime backend.
  • Required access: Network-level reachability to the affected endpoints; no valid credentials or account are required.
  • Trigger point: Directly invoking test/management endpoints with crafted requests that cause outbound SMS/Call/Email/WhatsApp actions or initiate phone number purchases.
  • Why exploitation is possible: The affected routes failed to enforce authentication and authorization, treating all incoming requests as implicitly trusted operations.

Why this happens

This issue stems from missing authentication on sensitive operational endpoints responsible for managing notification channels and purchasing phone numbers.

In access-controlled web applications, any action that triggers external communication or allocates billable resources should require user verification and appropriate authorization checks.

Here, the implementation either skipped or misconfigured the middleware/guard responsible for enforcing authentication on these routes, aligning with CWE-306: Missing Authentication for Critical Function.

As a result, unauthenticated clients could perform operations intended only for privileged, authenticated users.

Potential impact

  • Unauthenticated abuse of SMS, call, email, and WhatsApp channels for spam or phishing campaigns.
  • Unauthorized purchase of phone numbers, leading to unexpected financial charges.
  • Exhaustion of notification service quotas or rate limits, reducing availability for legitimate monitoring alerts.
  • Reputational damage due to association with unsolicited or malicious communications.
  • Potential blocking or blacklisting by third-party communication providers because of abusive traffic patterns.

General mitigation guidance

Mitigation should focus on enforcing strict access control around critical operational endpoints and minimizing what unauthenticated users can do by default.

Useful patterns include:

  • Applying a consistent authentication middleware or gateway in front of all state-changing or resource-consuming routes, with explicit allowlists for public endpoints.
  • Treating notification execution and phone number provisioning as privileged actions, requiring authenticated sessions and role-based authorization checks.
  • Implementing rate limiting, quotas, and anomaly detection for outbound communication operations to limit damage if access controls fail.
  • Separating internal administrative APIs from public-facing APIs, ideally via distinct hosts or network segments.
  • Designing secure defaults in routing configuration so that new endpoints are private unless explicitly exposed.

How teams detect issues like this

Detection typically involves a combination of code-level and runtime checks:

  • Static analysis / code scanning: Look for routes that invoke notification sending or resource provisioning APIs without passing through authentication/authorization middleware.
  • Code review signals: Flag any controller or handler that can send messages, perform purchases, or modify notification settings, and verify that it enforces identity and role checks.
  • Configuration review: Examine routing and gateway configs to ensure critical paths are not listed as public or bypassing security filters.
  • Runtime monitoring: Analyze logs for notification actions initiated from anonymous or unknown users, unusual spikes in messaging volume, or repeated calls from unauthenticated IPs.
  • Security testing: Use automated API testing or fuzzing tools to probe for sensitive actions accessible without valid credentials.

Sources

SourceLink
github.comgithub.com/OneUptime/oneuptime/commit/9adbd04538714740506708d6fa610e433be4d2a4
github.comgithub.com/OneUptime/oneuptime/releases/tag/10.0.42
github.comgithub.com/OneUptime/oneuptime/security/advisories/GHSA-q253-6wcm-h8hp

Frequently asked

questions

Yes. If the affected endpoints are exposed over the internet, a remote attacker can exploit them without any authentication, as long as they can reach the OneUptime API.

Only network access to the vulnerable endpoints is required. The attacker does not need a user account, API key, or session token to trigger notifications or phone number purchases.

Enforce mandatory authentication and authorization for all critical functions, especially those that send messages or create billable resources, by routing them through well-tested security middleware and applying least-privilege role checks.

Adopt secure-by-default routing conventions, where new endpoints are private unless explicitly marked public; centralize authentication and authorization logic; add automated tests and code review checklists for any functionality that triggers external communications or provisioning actions.

Find out what's already
exploitable in your codebase.