Executive brief
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.
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