Vulnerability Description
OneUptime is an open-source monitoring and observability platform. Prior to version 10.0.42, multiple notification API endpoints are registered without authentication middleware, while sibling endpoints in the same codebase correctly use ClusterKeyAuthorization.isAuthorizedServiceMiddleware. These endpoints are externally reachable via the Nginx proxy at /notification/. Combined with a projectId leak from the public Status Page API, an unauthenticated attacker can purchase phone numbers on the victim's Twilio account and delete all existing alerting numbers. This issue has been patched in version 10.0.42.
CVSS Score
HIGH
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Hackerbay | Oneuptime | < 10.0.42 |
Related Weaknesses (CWE)
References
- https://github.com/OneUptime/oneuptime/commit/9adbd04538714740506708d6fa610e433bPatch
- https://github.com/OneUptime/oneuptime/releases/tag/10.0.42ProductRelease Notes
- https://github.com/OneUptime/oneuptime/security/advisories/GHSA-6wc5-rhvj-cx7fExploitMitigationVendor Advisory
FAQ
What is CVE-2026-34759?
CVE-2026-34759 is a vulnerability with a CVSS score of 8.1 (HIGH). OneUptime is an open-source monitoring and observability platform. Prior to version 10.0.42, multiple notification API endpoints are registered without authentication middleware, while sibling endpoin...
How severe is CVE-2026-34759?
CVE-2026-34759 has been rated HIGH with a CVSS base score of 8.1/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-34759?
Check the references section above for vendor advisories and patch information. Affected products include: Hackerbay Oneuptime.