Is CVE-2026-34759 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-34759 being exploited in the wild.

How severe is CVE-2026-34759?

High severity, with a CVSS score of 8.1, published 2 April 2026.

Is there a fix for CVE-2026-34759?

A patch was published on 2026-03-31: Version 10.0.42 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-34759 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-34759?

Check whether you run 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.

CVE-2026-34759: OneUptime missing authorization in notification API endpoints

CVE-2026-34759 · Severity: high · CVSS 8.1 · Published 2026-04-02

OneUptime is an open-source platform used by businesses to monitor their digital services and notify staff of outages. A security flaw allows unauthorized individuals to access sensitive notification settings without a password. This could allow an attacker to incur significant financial costs by purchasing phone numbers on the company's Twilio account, disable emergency alerts by deleting existing phone numbers, or potentially access email server credentials.

Technologies: OneUptime. Vendors: OneUptime.

Quick answers

Is CVE-2026-34759 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-34759 being exploited in the wild.
How severe is CVE-2026-34759?: High severity, with a CVSS score of 8.1, published 2 April 2026.
Which products and versions are affected?: OneUptime < 10.0.42.
Is there a fix for CVE-2026-34759?: A patch was published on 2026-03-31: Version 10.0.42 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-34759 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-34759?: Check whether you run 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

Multiple notification API endpoints in 'App/FeatureSet/Notification/API/PhoneNumber.ts' (including /purchase, /list-owned, and /release) were registered without authentication middleware. These endpoints are reachable via the Nginx proxy at '/notification/'. While these routes require a 'projectId', this UUID is leaked via the public Status Page API. An attacker can exploit this to purchase phone numbers on the victim's Twilio account, enumerate owned numbers, and delete them to disable call-based alerting. Additionally, the SMTP configuration and WhatsApp test endpoints were found to be unauthenticated, potentially exposing SMTP credentials. The issue is fixed in version 10.0.42 by adding 'ClusterKeyAuthorization.isAuthorizedServiceMiddleware' to the affected routes.

Affected products

OneUptime OneUptime < 10.0.42

Timeline

2026-03-30: advisory: Vendor security advisory published via GitHub
2026-03-31: patched: Version 10.0.42 released
2026-04-02: disclosed: CVE-2026-34759 published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.